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 read 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>

Getting Started with Skills

Skill使用入门

MANDATORY FIRST RESPONSE PROTOCOL

强制首次响应流程

Before responding to ANY user message, you MUST complete this checklist:
  1. ☐ List available skills in your mind
  2. ☐ Ask yourself: "Does ANY skill match this request?"
  3. ☐ If yes → Use the Skill tool to read and run the skill file
  4. ☐ Announce which skill you're using
  5. ☐ Follow the skill exactly
Responding WITHOUT completing this checklist = automatic failure.
在回应用户的任何消息之前，你必须完成以下检查清单：
  1. ☐ 在脑海中列出可用的Skill
  2. ☐ 自问：“是否有任何Skill匹配该请求？”
  3. ☐ 如果是 → 使用Skill工具读取并运行Skill文件
  4. ☐ 宣布你将使用哪个Skill
  5. ☐ 严格遵循该Skill的要求
未完成此检查清单就直接回复 = 自动判定失败。

Critical Rules

核心规则

  1. Follow mandatory workflows. Brainstorming before coding. Check for relevant skills before ANY task.
  2. Execute skills with the Skill tool
  1. 遵循强制工作流：编码前先进行头脑风暴。在执行任何任务前先检查是否有相关Skill。
  2. 使用Skill工具执行Skill

Common Rationalizations That Mean You're About To Fail

预示你即将失败的常见借口

If you catch yourself thinking ANY of these thoughts, STOP. You are rationalizing. Check for and use the skill.
  • "This is just a simple question" → WRONG. Questions are tasks. Check for skills.
  • "I can check git/files quickly" → WRONG. Files don't have conversation context. Check for skills.
  • "Let me gather information first" → WRONG. Skills tell you HOW to gather information. Check for skills.
  • "This doesn't need a formal skill" → WRONG. If a skill exists for it, use it.
  • "I remember this skill" → WRONG. Skills evolve. Run the current version.
  • "This doesn't count as a task" → WRONG. If you're taking action, it's a task. Check for skills.
  • "The skill is overkill for this" → WRONG. Skills exist because simple things become complex. Use it.
  • "I'll just do this one thing first" → WRONG. Check for skills BEFORE doing anything.
Why: Skills document proven techniques that save time and prevent mistakes. Not using available skills means repeating solved problems and making known errors.
If a skill for your task exists, you must use it or you will fail at your task.
如果你发现自己有以下任何想法，请立即停止。你在找借口。请检查并使用相应的Skill。
  • “这只是个简单的问题” → 错误。问题也是任务。请检查Skill。
  • “我可以快速查看git/文件” → 错误。文件没有对话上下文。请检查Skill。
  • “我先收集信息” → 错误。Skill会告诉你如何收集信息。请检查Skill。
  • “这个不需要正式的Skill” → 错误。如果存在对应的Skill，就必须使用。
  • “我记得这个Skill” → 错误。Skill会更新。请使用当前版本。
  • “这不算一个任务” → 错误。只要你在采取行动，就是任务。请检查Skill。
  • “这个Skill对于这个任务来说大材小用了” → 错误。Skill的存在正是因为简单的事情可能变得复杂。请使用它。
  • “我先做这一件小事” → 错误。在做任何事情之前先检查Skill。
原因：Skill记录了经过验证的技术，可以节省时间并避免错误。不使用可用的Skill意味着重复解决已经解决的问题，并且会犯已知的错误。
如果存在适用于你任务的Skill，你必须使用它，否则你的任务会失败。

Skills with Checklists

带检查清单的Skill

If a skill has a checklist, YOU MUST create TodoWrite todos for EACH item.
Don't:
  • Work through checklist mentally
  • Skip creating todos "to save time"
  • Batch multiple items into one todo
  • Mark complete without doing them
Why: Checklists without TodoWrite tracking = steps get skipped. Every time. The overhead of TodoWrite is tiny compared to the cost of missing steps.
如果某个Skill包含检查清单，你必须为每一项创建TodoWrite待办事项。
禁止：
  • 仅在脑海中过一遍检查清单
  • 以“节省时间”为借口跳过创建待办事项
  • 将多个项合并为一个待办事项
  • 未执行就标记为完成
原因：没有TodoWrite跟踪的检查清单=步骤会被跳过，每次都是如此。TodoWrite的操作成本与遗漏步骤的代价相比微不足道。

Announcing Skill Usage

宣布Skill的使用

Before using a skill, announce that you are using it. "I'm using [Skill Name] to [what you're doing]."
Examples:
  • "I'm using the brainstorming skill to refine your idea into a design."
  • "I'm using the test-driven-development skill to implement this feature."
Why: Transparency helps your human partner understand your process and catch errors early. It also confirms you actually read the skill.
在使用Skill之前，宣布你将使用它。 “我正在使用[Skill名称]来[你的操作内容]。”
示例：
  • “我正在使用头脑风暴Skill将你的想法细化为设计方案。”
  • “我正在使用测试驱动开发Skill来实现这个功能。”
原因：透明化有助于你的人类伙伴理解你的流程，并尽早发现错误。这也能确认你确实阅读了该Skill。

About these skills

关于这些Skill

Many skills contain rigid rules (TDD, debugging, verification). Follow them exactly. Don't adapt away the discipline.
Some skills are flexible patterns (architecture, naming). Adapt core principles to your context.
The skill itself tells you which type it is.
许多Skill包含严格的规则（TDD、调试、验证）。 严格遵循这些规则。不要削弱其中的约束性要求。
有些Skill是灵活的模式（架构、命名）。 根据你的上下文调整核心原则。
Skill本身会告诉你它属于哪种类型。

Instructions ≠ Permission to Skip Workflows

指令≠跳过工作流的许可

Your human partner's specific instructions describe WHAT to do, not HOW.
"Add X", "Fix Y" = the goal, NOT permission to skip brainstorming, TDD, or RED-GREEN-REFACTOR.
Red flags: "Instruction was specific" • "Seems simple" • "Workflow is overkill"
Why: Specific instructions mean clear requirements, which is when workflows matter MOST. Skipping process on "simple" tasks is how simple tasks become complex problems.
你的人类伙伴的具体指令描述的是要做什么，而不是怎么做。
“添加X”、“修复Y”=目标，而非跳过头脑风暴、TDD或RED-GREEN-REFACTOR的许可。
危险信号： “指令很具体” • “看起来很简单” • “工作流程大材小用”
原因：具体的指令意味着明确的需求，而这正是工作流最重要的时候。在“简单”任务上跳过流程，正是简单任务演变成复杂问题的原因。

Summary

总结

Starting any task:
  1. If relevant skill exists → Use the skill
  2. Announce you're using it
  3. Follow what it says
Skill has checklist? TodoWrite for every item.
Finding a relevant skill = mandatory to read and use it. Not optional.
开始任何任务时：
  1. 如果存在相关Skill → 使用该Skill
  2. 宣布你正在使用它
  3. 严格遵循其要求
Skill带有检查清单？ 为每一项创建TodoWrite待办事项。
找到相关Skill=必须阅读并使用它。没有选择余地。