Stats
Actions
Tags
From superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
How this skill is triggered — by the user, by Claude, or both
Slash command
/superpowers:using-superpowersThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill.
If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill.
IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
In Claude Code: Use the Skill tool. When you invoke a skill, its content is loaded and presented to you — follow it directly.
Invoke relevant or requested skills BEFORE any response or action. Even a 1% chance a skill might apply means that you should invoke the skill to check.
When multiple skills could apply, use this order:
| Thought | Reality |
|---|---|
| "This is just a simple question" | Questions are tasks. Check for skills. |
| "I need more context first" | Skill check comes BEFORE clarifying questions. |
| "This doesn't need a formal skill" | If a skill exists, use it. |
| "I'll just do this one thing first" | Check BEFORE doing anything. |
Rigid (TDD, debugging): Follow exactly. Don't adapt away discipline. Flexible (patterns): Adapt principles to context.
The skill itself tells you which.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub jscomet/superpowers --plugin superpowers