using-superpowers
/using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
- Author
- bordenet ↗
- Repository
- superpowers-plus ↗
- Licence
- MIT
- Last repository change
- 06.10.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 06.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Original author description
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
How it works
- When to Use
- Instruction Priority
- How to Access Skills
- Platform Adaptation
- The Rule
- Red Flags
- Skill Priority
- Skill Types
- User Instructions
SKILL.md preview
---
name: using-superpowers
source: superpowers-plus
triggers: ["session start", "using superpowers"]
anti_triggers: []
description: Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
summary: "Use when: starting any conversation. Establishes skill invocation protocol."
coordination:
group: meta
order: 0
requires: []
enables: []
escalates_to: []
internal: false
composition:
consumes: [user-request]
produces: [skill-invocation-decision]
capabilities: [skill-routing, session-initialization, protocol-enforcement]
priority: 10
---
<SUBAGENT-STOP>
If you were dispatched as a subagent to execute a specific task, skip this skill.
</SUBAGENT-STOP>
<EXTREMELY-IMPORTANT>
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.
This is not negotiable. This is not optional. You cannot rationalize your way out of this.
</EXTREMELY-IMPORTANT>
## When to Use
- At the very start of every conversation — establishes which skills are available and how to invoke them
- When you need to choose between skills for the current task
- When a user asks how to invoke or configure superpowers
**NOT when:** already mid-task with skills loaded — the session protocol fires once at start, not repeatedly.
## Instruction Priority
Superpowers skills override default system prompt behavior, but **user instructions always take precedence**:
1. **User's explicit instructions** (CLAUDE.md, GEMINI.md, AGENTS.md, direct requests) — highest priority
2. **Superpowers skills** — override default system behavior where they conflict
3. **Default system prompt** — lowest priority
If CLAUDE.md, GEMINI.md, or AGENTS.md says "don't use TDD" and a skill says "always use TDD," follow the user's instructions. The user is in control.
## How to Access Skills
**In Augment Code:** A compact skill index (name, description, triggers) is injected at session bootstrap — the same index-then-dispatch flow used on other non-native platforms (see the AI-Native Trigger Matching diagram in `docs/DESIGN.md`). When a trigger matches, load the full skill via this repo's bootstrap CLI's `use-skill` command rather than reading the file directly. Once loaded, native platform tools are available directly, without the MCP-style naming prefix some other platforms use.
**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 Copilot CLI:** Use the `skill` tool. Skills are auto-discovered from installed plugins. The `skill` tool works the same as Claude Code's `Skill` tool.
**In Gemini CLI:** Skills activate via the `activate_skill` tool. Gemini loads skill metadata at session start and activates the full content on demand.
**In other environments:** Check your platform's documentation for how skills are loaded.
## Platform Adaptation
Skills use Claude Code tool names by default, including MCP-server tool names in Claude Code's own naming convention. On platforms with different tool-naming conventions — including Augment Code, where native tools are called directly without that MCP-style prefix — substitute the equivalent native tool for any Claude-Code-specific tool name a skill references. For Copilot CLI: see `references/copilot-tools.md`. For Codex: see `references/codex-tools.md`. Gemini CLI gets the tool mapping via GEMINI.md.
# 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.
```dot
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:
1. **Process skills first** (brainstorming, debugging) - these determine HOW to approach the task
2. **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.
Files in this package (4)
- skill.md 7 KB
- references/codex-tools.md 4 KB
- references/copilot-tools.md 2 KB
- references/gemini-tools.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · bordenet/superpowers-plus | 100 | MIT |
| coco-research/coco | 100 | MIT |
| osmontero/opencode-skills | 100 | MIT |
| seaworld008/commonly-used-high-value-skills | 100 | MIT |
| chinkan/RustFox | 100 | MIT |
| VoDaiLocz/kilo-kit-mcp | 100 | Apache-2.0 |
| sickn33/agentic-awesome-skills | 100 | MIT |
| liyunxuanyu/dsh-zcode-port | 100 | MIT |
| LiHongwei-cn/lihongwei-cn | 100 | MIT |
Database snapshot: 13.11.2026 · package version 7421c4aeeff1 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100using-werkstatt
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions - 100using-ultraship
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions - 100using-systematic
Use when starting any conversation - establishes how to find and use skills, requiring skill tool invocation before ANY response including clarifying questions - 100using-methodology
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions - 100using-quirk
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions - 100using-loopkit
Use when starting any conversation in a loopkit-enabled project - establishes how to find and use loopkit's 49 skills, requiring skill invocation before ANY response including clarifying questions.