SuperAPI AI Directory

using-superpowers

General & other

View repository

Updated 10-16 09:44

About this skill

If a skill applies to your task, you have no choice. You must use it.

This is non-negotiable. It is not optional. You cannot escape through rationalization.

Instruction Priority

Superpowers skills override default system prompt behavior, butuser instructions always have the highest priority:

  1. The 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 "do not 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 contents are loaded and presented to you—just follow them directly. Never use the Read tool to read skill files.

In Copilot CLI: Use the skill tool. Skills are automatically discovered from installed plugins.skill The tool works the same way as Claude Code's Skill tool.

In Hermes Agent: Use the skill_view tool to load skills. Hermes supports three levels of progressive loading:skills_list browse → skill_view(name) load full content → skill_view(name, path) view referenced files.

In Gemini CLI: Skills are activated through the activate_skill tool. Gemini loads skill metadata at the start of the session and activates the full content on demand.

In other environments: Check your platform documentation for how skills are loaded.

Platform Adaptation

Skills use Claude Code's tool names. Non-CC platforms: see references/copilot-tools.md(Copilot CLI)、references/hermes-tools.md(Hermes Agent)、references/codex-tools.md(Codex) for tool mappings. Gemini CLI users get tool mappings automatically via GEMINI.md.

Using Skills

Rules

Invoke the relevant or requested skill before any response or action. Even if there is only a 1% chance a skill applies, you should invoke that skill to check. If after invoking it you find the skill does not fit the current situation, you do not need to use it.

digraph skill_flow {
    "收到用户消息" [shape=doublecircle];
    "即将进入 EnterPlanMode?" [shape=doublecircle];
    "已经头脑风暴过?" [shape=diamond];
    "调用头脑风暴技能" [shape=box];
    "可能有技能适用?" [shape=diamond];
    "调用 Skill 工具" [shape=box];
    "宣布:'使用 [技能] 来 [目的]'" [shape=box];
    "有检查清单?" [shape=diamond];
    "为每个条目创建 TodoWrite 待办" [shape=box];
    "严格遵循技能" [shape=box];
    "响应(包括澄清)" [shape=doublecircle];

    "即将进入 EnterPlanMode?" -> "已经头脑风暴过?";
    "已经头脑风暴过?" -> "调用头脑风暴技能" [label="否"];
    "已经头脑风暴过?" -> "可能有技能适用?" [label="是"];
    "调用头脑风暴技能" -> "可能有技能适用?";

    "收到用户消息" -> "可能有技能适用?";
    "可能有技能适用?" -> "调用 Skill 工具" [label="是,哪怕只有 1%"];
    "可能有技能适用?" -> "响应(包括澄清)" [label="确定不适用"];
    "调用 Skill 工具" -> "宣布:'使用 [技能] 来 [目的]'";
    "宣布:'使用 [技能] 来 [目的]'" -> "有检查清单?";
    "有检查清单?" -> "为每个条目创建 TodoWrite 待办" [label="是"];
    "有检查清单?" -> "严格遵循技能" [label="否"];
    "为每个条目创建 TodoWrite 待办" -> "严格遵循技能";
}

Red Lines

These thoughts mean stop—you are rationalizing:

Thought Reality
"This is just a simple question" The question is the task. Check for a skill.
"I need to understand more context first" Skill check comes before clarifying questions.
"Let me explore the codebase first" The skill tells you how to explore. Check first.
"I can quickly check git/files" Files lack conversation context. Check for a skill.
"Let me gather information first" The skill tells you how to gather information.
"This doesn't need a formal skill" If a skill exists, use it.
"I remember this skill" Skills are iteratively updated. Read the current version.
"This doesn't count as a task" Action = task. Check the skill.
"The skill is making a big deal out of nothing" Simple things become complicated. Use it.
"Let me just do this one thing first" Check before doing anything.
"Doing it this way feels efficient" 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 may apply, use this order:

  1. Process skills take priority(brainstorming, debugging) - these determine how to handle the task
  2. Implementation skills come second(frontend design, mcp-builder) - these guide execution

"Let's build X" → brainstorm first, then use implementation skills. "Fix this bug" → debug first, then use domain-specific skills.

Chinese-Specific Skill Routing

When the following scenarios are detected,you mustprioritize invoking the corresponding Chinese-specific skills:

Scenario Invoke Skill
Code review and the team communicates in Chinese superpowers:chinese-code-review
Using Gitee/Coding/JiHu GitLab superpowers:chinese-git-workflow
Writing Chinese technical documentation or README superpowers:chinese-documentation
Writing git commit messages (Chinese projects) superpowers:chinese-commit-conventions
Building MCP servers/tools superpowers:mcp-builder

Criteria for judgment:

  • The project has Chinese comments, a Chinese README, or a .gitee directory → enable the Chinese skill series
  • The commit history contains Chinese → use Chinese commit conventions
  • The user communicates in Chinese → use Chinese for all output, and prioritize Chinese-specific skills

Chinese-Specific Skills and Translation Skillsare used in combination, not mutually exclusive. For example: when doing a code review, use requesting-code-review (process) + chinese-code-review (style) at the same time.

Skill Types

Rigid(TDD, debugging): follow strictly. Do not deviate from the discipline.

Flexible(patterns): adapt the principles according to context.

The skill itself will tell you which type it is.

User Instructions

Instructions say what to do, not how to do it. "Add X" or "fix Y" does not mean skipping the workflow.