Back to Details

using-superpowers

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
<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>
<EXTREMELY-IMPORTANT> 如果你认为哪怕有1%的可能性某个Skill适用于你正在做的事情，你绝对必须调用该Skill。
如果某个Skill适用于你的任务，你别无选择。必须使用它。
这没有商量余地，也不是可选项。你不能找理由不这么做。 </EXTREMELY-IMPORTANT>

How to Access Skills

如何访问Skill

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 other environments: Check your platform's documentation for how skills are loaded.
在Claude Code中： 使用
Skill
工具。调用Skill时，其内容会被加载并呈现给你——请直接遵循该内容。永远不要对Skill文件使用Read工具。
在其他环境中： 查看你所使用平台的文档，了解Skill的加载方式。

Using Skills

使用Skill

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

    "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";
}
在任何回复或操作之前，调用相关或被要求的Skill。 哪怕只有1%的可能性Skill适用，你也应该调用它来确认。如果调用的Skill最终不适合当前情况，你可以不用它。
dot
digraph skill_flow {
    "User message received" [shape=doublecircle];
    "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];

    "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:
ThoughtReality
"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。
"我需要先了解更多背景信息"检查Skill要在提出澄清问题之前进行。
"我先浏览一下代码库"Skill会告诉你如何浏览。先检查Skill。
"我可以快速查看git/文件"文件缺乏对话背景。请检查是否有适用的Skill。
"我先收集一些信息"Skill会告诉你如何收集信息。
"这个不需要正式的Skill"如果存在适用的Skill，就使用它。
"我记得这个Skill"Skill会更新。请读取当前版本。
"这不算是任务"任何行动都是任务。请检查Skill。
"用这个Skill大材小用了"简单的事情可能变得复杂。使用它。
"我先做这一件小事"做任何事情之前都要先检查Skill。
"这样做感觉很高效"无条理的行动会浪费时间。Skill可以避免这种情况。
"我知道那是什么意思"了解概念≠使用Skill。调用它。

Skill Priority

Skill优先级

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可能适用时，请按照以下顺序选择：
  1. 优先使用流程类Skill（头脑风暴、调试）——这些Skill决定了处理任务的方式
  2. 其次是实现类Skill（frontend-design、mcp-builder）——这些Skill指导执行
例如：“我们来构建X” → 先使用头脑风暴类Skill，再使用实现类Skill。 “修复这个bug” → 先使用调试类Skill，再使用领域特定Skill。

Skill Types

Skill类型

Rigid (TDD, debugging): Follow exactly. Don't adapt away discipline.
Flexible (patterns): Adapt principles to context.
The skill itself tells you which.
严格型（TDD、调试）：严格遵循。不要偏离规范。
灵活型（模式）：根据上下文调整原则。
Skill本身会说明它属于哪种类型。

User Instructions

用户指令

Instructions say WHAT, not HOW. "Add X" or "Fix Y" doesn't mean skip workflows.
用户指令告诉你要做什么（WHAT），而不是怎么做（HOW）。“添加X”或“修复Y”并不意味着可以跳过工作流程。