using-superpowers

其他社区 @obra

信任分: 88/100
兼容 Agent: 1

速查档案只列事实：领域、Agent、信任分、作者、原文章节。装与不装请看下方作者解读。

领域: 通用
兼容 Agent: Claude Code
信任分: 88 / 100 · 社区维护
作者 / 版本 / 许可: @obra · 未声明 license
安装命令数: 1 条

需要注意： 未限定 allowed-tools，默认拥有全部工具权限。

想读作者英文原文？ ↓ 滚到正文区切换 · 在 GitHub 查看 ↗

解读由编辑根据原文凝练而成，命令、链接、术语均与作者原文一致；想看完整论述请切到右侧

using-superpowers 是 superpowers 体系的「使用守则」：你必须把 skills 当成第一层指令源——只要有 1% 可能命中当前任务，必须 invoke。但用户的显式指令永远凌驾于 skill 之上。

优先级

1）用户显式指令（CLAUDE.md / GEMINI.md / AGENTS.md / 直接对话）= 最高；2）superpowers skills——在与默认 system prompt 冲突时覆盖默认；3）默认 system prompt = 最低。CLAUDE.md 说「不要 TDD」、skill 说「永远 TDD」时，听用户的——用户握控制权。

铁律

"IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT." 哪怕只有 1% 可能命中也必须先 invoke 检查；如果 invoke 后发现这个 skill 跟当前情境不对，再放弃。SUBAGENT-STOP：被派为 subagent 干具体任务时跳过本 skill——subagent 拿到的 prompt 已是「精剪好的任务卡」，不该再触发 skill 路由。

Skill 的访问方式

Claude Code：用 Skill tool；invoke 后 skill 内容被加载并展示给你，跟着做即可——永远不要用 Read 去打开 skill 文件
Copilot CLI：skill tool（从已装 plugin auto-discover，等价于 Claude Code 的 Skill）
Gemini CLI：activate_skill tool（session start 加载 metadata，需要时才激活完整内容）
其他平台：查平台文档

平台适配

Skills 用的是 Claude Code 的 tool 名。非 CC 平台：references/copilot-tools.md（Copilot CLI）、references/codex-tools.md（Codex）有 tool 等价映射；Gemini CLI 通过 GEMINI.md 自动加载映射。

适合的场景

第一次接 superpowers skills，理解「skill > default」的优先级
多平台共用同一组 skill（Claude Code / Copilot / Gemini），要知道每家怎么 invoke
调试「为什么 agent 不按 skill 来」——多半是没遵守这条铁律

何时不要用

你是被派活的 subagent：按 SUBAGENT-STOP 跳过即可
当前任务无任何 skill 适配：本守则会让你 invoke 一下确认无命中即可

配套

writing-skills（怎么写 skill 让其他 agent 容易命中）、skill-creator（写新 skill 的元 skill）、template-skill（骨架）、subagent-driven-development（subagent 与本守则的边界）。

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

Instruction Priority

Superpowers skills override default system prompt behavior, but user instructions always take precedence:

User's explicit instructions (CLAUDE.md, GEMINI.md, AGENTS.md, direct requests) — highest priority
Superpowers skills — override default system behavior where they conflict
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 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. Non-CC platforms: see references/copilot-tools.md (Copilot CLI), references/codex-tools.md (Codex) for tool equivalents. Gemini CLI users get the tool mapping loaded automatically 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.

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.