using-superpowers
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseUsing Skills
使用Skill
Skills are specialized workflows that improve quality for specific task types. Use them when they apply - don't skip them by rationalizing, but also don't invoke them ritualistically.
Skill是针对特定任务类型提升工作质量的专业化工作流。在适用时使用它们——不要找借口跳过，但也不要机械地调用它们。
When to Load a Skill
何时加载Skill
DO load skills when:
- Starting a complex or multi-step task
- The task clearly matches a skill's description (code review, debugging, planning, etc.)
- You're unsure how to approach something and a skill might help
- The user explicitly requests a skill-based workflow
DON'T load skills when:
- Answering simple questions or having conversation
- Doing trivial file reads or small edits
- The task is straightforward and no skill adds value
- You already know the skill's content from this session
应加载Skill的场景：
- 启动复杂或多步骤任务时
- 任务与Skill的描述明确匹配时（如代码审查、调试、规划等）
- 你不确定如何处理某件事，而Skill可能提供帮助时
- 用户明确请求基于Skill的工作流时
不应加载Skill的场景：
- 回答简单问题或进行日常对话时
- 执行简单的文件读取或小修改时
- 任务流程清晰，Skill无法带来额外价值时
- 你在本次会话中已经了解该Skill的内容时
How to Use Skills
如何使用Skill
When a skill applies:
- Load it with the Skill tool
- Announce briefly: "Using [skill] for [purpose]"
- If it has a checklist, create todos
- Follow the skill's workflow
当Skill适用时：
- 使用Skill工具加载它
- 简要告知："正在为[目的]使用[skill]"
- 如果Skill包含检查清单，创建待办事项
- 遵循Skill的工作流
Avoiding Common Mistakes
避免常见错误
Under-using skills (rationalizing):
| Thought | Consider |
|---|---|
| "I'll just do this quickly" | Would a skill improve quality? |
| "This doesn't need a formal process" | Is there a skill that applies? |
| "I remember how this works" | Skills evolve - reload if unsure |
| "Let me explore first" | Some skills guide exploration |
Over-using skills (ritual compliance):
| Thought | Reality |
|---|---|
| "I must invoke skills on every message" | Only when they add value |
| "Let me check for mandatory skills" | Skills aren't rituals |
| "Confirming skill protocol compliance" | Just do the work |
Skill使用不足（找借口）：
| 想法 | 思考方向 |
|---|---|
| "我快速做一下就好" | Skill能提升工作质量吗？ |
| "这个不需要正式流程" | 有没有适用的Skill？ |
| "我记得这个怎么操作" | Skill会迭代——不确定时重新加载 |
| "我先探索一下" | 有些Skill可以指导探索过程 |
Skill使用过度（机械合规）：
| 想法 | 实际情况 |
|---|---|
| "我必须在每条消息中调用Skill" | 仅在Skill能带来价值时使用 |
| "我看看有没有强制要求的Skill" | Skill不是仪式 |
| "确认Skill协议合规性" | 直接开展工作即可 |
Skill Priority
Skill优先级
When multiple skills could apply:
- Process skills first (brainstorming, debugging) - these determine HOW to approach
- Implementation skills second - these guide execution
Examples:
- "Let's build X" → brainstorming first, then implementation
- "Fix this bug" → debugging first, then domain-specific skills
当多个Skill都适用时：
- 先使用流程类Skill（如头脑风暴、调试）——这些Skill决定处理方式
- 再使用实现类Skill——这些Skill指导执行过程
示例：
- "我们来构建X" → 先进行头脑风暴，再执行实现
- "修复这个bug" → 先进行调试，再使用领域特定Skill
Skill Types
Skill类型
Rigid (TDD, debugging): Follow the process exactly.
Flexible (patterns): Adapt principles to context.
The skill itself indicates which type it is.
严格型（如TDD、调试）：严格遵循流程。
灵活型（如模式类）：根据上下文调整原则。
Skill本身会标注其类型。
Remember
注意事项
- Skills improve quality for complex tasks
- Simple tasks don't need skill overhead
- If you're announcing "checking mandatory protocols" you've gone too far
- Just use skills naturally when they help
- Skill能提升复杂任务的工作质量
- 简单任务无需Skill的额外开销
- 如果你在说"检查强制协议"，那你做得太过了
- 只需在Skill有用时自然地使用它们