using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Install
git clone https://github.com/obra/superpowers /tmp/superpowers && ln -s /tmp/superpowers/skills/using-superpowers ~/.claude/skills/using-superpowers
From README
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.
More from this repo
systematic-debugging
Used when encountering any bug, test failure, or unexpected behavior, before proposing fixes
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying...
dispatching-parallel-agents
Used when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
