超能力技能使用指南：AI助手技能调用优先级与工作流程详解

using-superpowers by obra/superpowers

33,600 周安装量

107,700 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/obra/superpowers --skill using-superpowers

AI/机器学习开发生产力

🇨🇳中文介绍

如果某项技能适用于你的任务，你没有选择。你必须使用它。

这是不可协商的。这不是可选的。你不能通过合理化来逃避这一点。

指令优先级

超能力技能会覆盖默认的系统提示行为，但用户指令始终具有最高优先级：

用户的明确指令 (CLAUDE.md, GEMINI.md, AGENTS.md, 直接请求) — 最高优先级
超能力技能 — 在冲突时覆盖默认系统行为
默认系统提示 — 最低优先级

如果 CLAUDE.md、GEMINI.md 或 AGENTS.md 说"不要使用 TDD"，而某个技能说"始终使用 TDD"，请遵循用户的指令。用户是掌控者。

如何访问技能

在 Claude Code 中： 使用 Skill 工具。当你调用一个技能时，其内容会被加载并呈现给你——请直接遵循它。切勿对技能文件使用 Read 工具。

在 Gemini CLI 中： 技能通过 activate_skill 工具激活。Gemini 在会话开始时加载技能元数据，并按需激活完整内容。

在其他环境中： 请查阅你所在平台的文档，了解技能是如何加载的。

平台适配

技能使用 Claude Code 工具名称。对于非 CC 平台：请参阅 references/codex-tools.md (Codex) 以获取等效工具。Gemini CLI 用户通过 GEMINI.md 自动加载工具映射。

使用技能

规则

在任何响应或行动之前，调用相关或被请求的技能。 即使某项技能只有 1% 的可能性适用，你也应该调用该技能来检查。如果调用的技能最终不适合当前情况，你就不需要使用它。

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

相关 Skills

find-skills 技能搜索工具 - Vercel Labs 开源智能体技能包管理器

685,800 周安装

Vercel React 最佳实践指南 | 58条Next.js性能优化规则与代码重构

240,900 周安装

Vercel Web界面规范检查工具 - 自动检测代码是否符合Web设计指南

193,000 周安装

agent-browser 浏览器自动化工具 - Vercel Labs 命令行网页操作与测试

125,300 周安装

React 组合模式指南：Vercel 组件架构最佳实践，提升代码可维护性

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";
}

想法	现实
"这只是个简单的问题"	问题就是任务。检查是否有适用的技能。
"我需要先了解更多背景信息"	技能检查应在澄清问题之前进行。
"让我先探索一下代码库"	技能会告诉你如何探索。先检查。
"我可以快速检查一下 git/文件"	文件缺乏对话上下文。先检查技能。
"让我先收集信息"	技能会告诉你如何收集信息。
"这不需要正式的技能"	如果存在相关技能，就使用它。
"我记得这个技能"	技能会演变。阅读当前版本。
"这不算一个任务"	行动 = 任务。检查技能。
"这个技能太小题大做了"	简单的事情可能变得复杂。使用它。
"我先做这一件事"	在做任何事情之前先检查。
"这感觉很有成效"	无纪律的行动会浪费时间。技能可以防止这一点。
"我知道那是什么意思"	知道概念 ≠ 使用技能。调用它。

🇺🇸English

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 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/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.

Weekly Installs

33.6K

Repository

obra/superpowers

GitHub Stars

107.7K

First Seen

Jan 19, 2026

Security Audits

Gen Agent Trust HubWarn SocketWarn SnykPass

Installed on

opencode29.7K

codex28.8K

gemini-cli28.8K

github-copilot27.7K

amp26.3K

kimi-cli26.3K