meta-superpowers
Using Skills Effectively
Mandatory First-Response Protocol
Before responding to any user request:
- ☐ Mentally enumerate available skills.
- ☐ Ask: “Does ANY skill match this task?”
- ☐ If yes → Use the Skill tool to read/run it (do not rely on memory).
- ☐ Announce: “I’m using [Skill Name] to …”.
- ☐ Follow the skill exactly (brainstorming before coding, etc.).
Skipping this checklist is automatic failure.
Critical Rules
- Mandatory workflows – Brainstorming before coding, TDD, verification, etc. Instructions about WHAT to do never override HOW defined by skills.
- Execute via Skill tool – Always load the latest file; skills evolve.
More from tjboudreaux/cc-plugin-engineering-excellence
eng-tdd
Enforces disciplined RED-GREEN-REFACTOR cycle—write failing test first, watch it fail, write minimal code to pass, then refactor.
2eng-verification
Mandatory checklist before claiming work is complete—run the evidence-producing command, inspect output, and only then state a result.
2eng-performance
Guard latency, memory, battery, bandwidth, and gas/compute budgets by measuring before and after every change.
2eng-user-impact
Anchor every engineering decision in user value, measurable outcomes, accessibility, and cross-platform experience coherence.
2eng-observability
Design every change with traceability, diagnostics, and fast incident triage in mind across mobile, web, and web3 stacks.
2eng-quality-handoff
Deliver changes with clear communication, reviewer-ready context, and follow-up accountability.
2