Using Skills
The Rule
Invoke relevant or requested skills before any response or action, including clarifying questions. If there is even a 1% chance a skill applies, invoke it first. If the skill turns out not to apply, you can stop using it after checking.
In environments with a Skill tool, use that tool instead of reading skill files manually.
Legacy Quality Mode
Prioritize content quality over context minimization.
When a skill applies:
- Load the full primary
SKILL.md, not just its name or short description.
- If the skill is an alias/router, immediately load the downstream primary skill(s) it points to.
- If the skill references task guides, examples, scripts, templates, or troubleshooting notes that are relevant to the request, read those before acting.
- Do not skip QA gates, visual verification, command sequencing rules, edge-case notes, or tool-specific caveats to save context.
- Use progressive disclosure only to avoid clearly irrelevant files, not to avoid necessary operational instructions.
If context budget and quality conflict, choose quality and rely on later compaction rather than under-loading the skill.
Red Flags
Stop and check skills if you catch yourself thinking:
- "This is simple, I can skip the skill check"
- "I need more context first"
- "I'll explore files first"
- "I remember the skill already"
- "This one action doesn't count"
- "The skill is overkill"
Skill Priority
When multiple skills could apply, use this order:
- Process skills first (brainstorming, debugging) - these determine HOW to approach the task
- Implementation skills second (frontend-design, mcp-builder) - these guide execution
"Let's build X" means brainstorming first, then implementation skills.
"Fix this bug" means debugging first, then domain-specific skills.
Execution
After invoking a skill:
- Announce which skill you are using and why
- Load enough related skill material to execute at full quality, especially for Office documents, spreadsheets, data analysis, coding, debugging, frontend work, and reviews
- If the skill has a checklist, create a todo for each item
- Follow the skill exactly unless it explicitly says it is flexible
Rigid skills such as TDD or debugging must be followed literally. Pattern skills can be adapted, but only after they have been invoked.
User Instructions
Instructions say WHAT, not HOW. "Add X" or "Fix Y" doesn't mean skip workflows.
1---2name: using-superpowers3description: Use skills correctly.4---56# Using Skills78## The Rule910Invoke relevant or requested skills before any response or action, including clarifying questions. If there is even a 1% chance a skill applies, invoke it first. If the skill turns out not to apply, you can stop using it after checking.1112In environments with a Skill tool, use that tool instead of reading skill files manually.1314## Legacy Quality Mode1516Prioritize content quality over context minimization.1718When a skill applies:19201. Load the full primary `SKILL.md`, not just its name or short description.212. If the skill is an alias/router, immediately load the downstream primary skill(s) it points to.223. If the skill references task guides, examples, scripts, templates, or troubleshooting notes that are relevant to the request, read those before acting.234. Do not skip QA gates, visual verification, command sequencing rules, edge-case notes, or tool-specific caveats to save context.245. Use progressive disclosure only to avoid clearly irrelevant files, not to avoid necessary operational instructions.2526If context budget and quality conflict, choose quality and rely on later compaction rather than under-loading the skill.2728## Red Flags2930Stop and check skills if you catch yourself thinking:3132- "This is simple, I can skip the skill check"33- "I need more context first"34- "I'll explore files first"35- "I remember the skill already"36- "This one action doesn't count"37- "The skill is overkill"3839## Skill Priority4041When multiple skills could apply, use this order:42431. **Process skills first** (brainstorming, debugging) - these determine HOW to approach the task442. **Implementation skills second** (frontend-design, mcp-builder) - these guide execution4546"Let's build X" means brainstorming first, then implementation skills.47"Fix this bug" means debugging first, then domain-specific skills.4849## Execution5051After invoking a skill:5253- Announce which skill you are using and why54- Load enough related skill material to execute at full quality, especially for Office documents, spreadsheets, data analysis, coding, debugging, frontend work, and reviews55- If the skill has a checklist, create a todo for each item56- Follow the skill exactly unless it explicitly says it is flexible5758Rigid skills such as TDD or debugging must be followed literally. Pattern skills can be adapted, but only after they have been invoked.5960## User Instructions6162Instructions say WHAT, not HOW. "Add X" or "Fix Y" doesn't mean skip workflows.
kyrie66nb