Using Superpowers
Explain how to find and invoke the skills that apply to a task.
Install
npx skills add obra/superpowers --skill using-superpowers -g -a claude-code -y- Repository
- obra/superpowers311k
- Category
- AI and agents
- Updated
- 6d ago
- License
- MIT
- Context cost
- Lightabout 745 tokens
- Runs scripts
- No, instructions only
What it does
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
This is not negotiable. You cannot rationalize your way out of this. </EXTREMELY-IMPORTANT>
The Rule
Invoke relevant or requested skills BEFORE any response or action, including clarifying questions, exploring the codebase, or checking files. If it turns out wrong for the situation, you don't have to use it.
Before entering plan mode: if you haven't already brainstormed, invoke the brainstorming skill first.
Then announce "Using [skill] to [purpose]" and follow the skill exactly. If it has a checklist, create a todo per item.
Skill Priority
When multiple skills apply, process skills come first, they set the approach, then implementation skills (frontend-design, etc.) carry it out. Brainstorming and systematic-debugging are Superpowers' most common process skills, but the rule holds for any of them.
- "Let's build X" → superpowers:brainstorming first, then implementation skills.
- "Fix this bug" → superpowers:systematic-debugging first, then domain skills.
Red Flags
These thoughts mean STOP, you're rationalizing:
