using-superpowers 精选

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

编码 Claude Code Codex CLI Gemini CLI MIT 30 万

在 GitHub 打开

安装方式

cp -r skills/using-superpowers ~/.claude/skills/using-superpowers

把该 skill 目录放进客户端 skills 目录。不同客户端的目录可能不同，Claude Code 默认是 ~/.claude/skills/

整仓一次性获取：git clone --depth 1 https://github.com/obra/superpowers.git

依赖与权限

无需 API Key
无需联网
依赖外部命令：git
以上为按正文与 frontmatter 自动推断的信号，仅供参考；安装前建议先阅读原文。

触发场景

requiring skill invoca

SKILL.md 正文

来源 obra/superpowers@bb92a77 · 许可 MIT · 内容未修改

<SUBAGENT-STOP>

If you were dispatched as a subagent to execute a specific task, ignore 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. 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:

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.

Platform Adaptation

If your harness appears here, read its reference file for special instructions:

Claude Code: references/claude-code-tools.md
Codex: references/codex-tools.md
Pi: references/pi-tools.md
Antigravity: references/antigravity-tools.md
Hermes Agent: references/hermes-tools.md
Muse: references/muse-tools.md

User Instructions

User instructions (CLAUDE.md, AGENTS.md, GEMINI.md, etc, direct requests) take precedence over skills, which in turn override default behavior. Only skip skill workflows or instructions when your human partner has explicitly told you to.