using-superpowers
npx machina-cli add skill guanyang/antigravity-skills/using-superpowers --openclawIF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
This is not negotiable. This is not optional. You cannot rationalize your way out of this. </EXTREMELY-IMPORTANT>
How to Access Skills
In Claude Code: Use the Skill tool. When you invoke a skill, its content is loaded and presented to you—follow it directly. Never use the Read tool on skill files.
In other environments: Check your platform's documentation for how skills are loaded.
Using Skills
The Rule
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. If an invoked skill turns out to be wrong for the situation, you don't need to use it.
digraph skill_flow {
"User message received" [shape=doublecircle];
"About to EnterPlanMode?" [shape=doublecircle];
"Already brainstormed?" [shape=diamond];
"Invoke brainstorming skill" [shape=box];
"Might any skill apply?" [shape=diamond];
"Invoke Skill tool" [shape=box];
"Announce: 'Using [skill] to [purpose]'" [shape=box];
"Has checklist?" [shape=diamond];
"Create TodoWrite todo per item" [shape=box];
"Follow skill exactly" [shape=box];
"Respond (including clarifications)" [shape=doublecircle];
"About to EnterPlanMode?" -> "Already brainstormed?";
"Already brainstormed?" -> "Invoke brainstorming skill" [label="no"];
"Already brainstormed?" -> "Might any skill apply?" [label="yes"];
"Invoke brainstorming skill" -> "Might any skill apply?";
"User message received" -> "Might any skill apply?";
"Might any skill apply?" -> "Invoke Skill tool" [label="yes, even 1%"];
"Might any skill apply?" -> "Respond (including clarifications)" [label="definitely not"];
"Invoke Skill tool" -> "Announce: 'Using [skill] to [purpose]'";
"Announce: 'Using [skill] to [purpose]'" -> "Has checklist?";
"Has checklist?" -> "Create TodoWrite todo per item" [label="yes"];
"Has checklist?" -> "Follow skill exactly" [label="no"];
"Create TodoWrite todo per item" -> "Follow skill exactly";
}
Red Flags
These thoughts mean STOP—you're rationalizing:
| 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. |
| "Let me explore the codebase first" | Skills tell you HOW to explore. Check first. |
| "I can check git/files quickly" | Files lack conversation context. Check for skills. |
| "Let me gather information first" | Skills tell you HOW to gather information. |
| "This doesn't need a formal skill" | If a skill exists, use it. |
| "I remember this skill" | Skills evolve. Read current version. |
| "This doesn't count as a task" | Action = task. Check for skills. |
| "The skill is overkill" | Simple things become complex. Use it. |
| "I'll just do this one thing first" | Check BEFORE doing anything. |
| "This feels productive" | Undisciplined action wastes time. Skills prevent this. |
| "I know what that means" | Knowing the concept ≠ using the skill. Invoke it. |
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" → brainstorming first, then implementation skills. "Fix this bug" → debugging first, then domain-specific skills.
Skill Types
Rigid (TDD, debugging): Follow exactly. Don't adapt away discipline.
Flexible (patterns): Adapt principles to context.
The skill itself tells you which.
User Instructions
Instructions say WHAT, not HOW. "Add X" or "Fix Y" doesn't mean skip workflows.
Source
git clone https://github.com/guanyang/antigravity-skills/blob/main/skills/using-superpowers/SKILL.mdView on GitHub Overview
using-superpowers is a meta-skill that enforces loading and following the correct skill before answering any user message. It requires invoking the Skill tool before any response, including clarifying questions, to determine the right approach. If a skill applies, it guides you to announce usage and, if applicable, create actionable tasks.
How This Skill Works
When a user message arrives, you assess potential skills and, if any could apply (even 1%), you immediately invoke the Skill tool to load the relevant content and follow it exactly. You must announce: 'Using [skill] to [purpose]' before proceeding. If the skill provides a checklist, you generate TodoWrite items and follow the skill's workflow; otherwise you respond as directed.
When to Use It
- At the start of every conversation to establish how to find and use skills
- Before asking clarifying questions to ensure the right skill is applied
- When multiple skills might apply, to determine the correct approach
- When a task may require following a skill's checklist or workflow
- Whenever you suspect a skill might apply (even a 1% chance) and must check
Quick Start
- Step 1: Detect potential skill applicability (even 1%).
- Step 2: Invoke the Skill tool to load the relevant skill.
- Step 3: Announce usage and follow the skill's steps before replying.
Best Practices
- Check for applicable skills before any response, even if it seems unnecessary
- Always invoke the Skill tool if a skill might apply, even by 1%
- Announce usage: 'Using [skill] to [purpose]' before responding
- Follow the skill exactly; use any checklists or outputs provided
- If the invoked skill is wrong for the situation, proceed without it
Example Use Cases
- A user asks for a planning approach; you invoke the planning skill first and then respond
- A question requires debugging steps; you load the debugging skill prior to answering
- You encounter ambiguity; you check for relevant skills before clarifying and still answer
- A task prompts a TodoWrite list; you generate actionable items per the skill's guidance
- A user asks for general info; no skill applies, so you respond normally after the check
