Back to Details

capability-activation

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

How to Access Skills

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

Using Skills

使用Skills

The Rule

规则

Check for skills BEFORE ANY RESPONSE. This includes clarifying questions. Even 1% chance means invoke the Skill tool first.
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";
}
在做出任何响应之前先检查是否有适用的Skills。 这包括澄清问题。哪怕只有1%的可能性，也要先调用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.
出现以下想法时请立即停止——你正在找借口：
想法实际情况
"这只是个简单问题"问题也是任务，需要检查是否有适用的Skills。
"我需要更多上下文信息"检查Skill要在提出澄清问题之前进行。
"我先探索一下代码库"Skills会告诉你如何探索，先检查。
"我可以快速查看git/文件"文件缺乏对话上下文，检查是否有适用的Skills。
"我先收集信息"Skills会告诉你如何收集信息。
"这个不需要正式的Skill"如果存在相关Skill，就必须使用。
"我记得这个Skill"Skills会更新，要查看当前版本。
"这不算任务"任何行动都是任务，检查是否有适用的Skills。
"用Skill太小题大做了"简单的事情可能变得复杂，必须使用Skill。
"我先做这一件小事"在做任何事情之前先检查。
"这感觉很高效"无纪律的行动会浪费时间，Skills能避免这种情况。

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. 先使用流程类Skills（头脑风暴、调试）——这些技能决定了处理任务的方式
  2. 再使用实现类Skills（frontend-design、mcp-builder）——这些技能指导执行
"我们来构建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"并不意味着可以跳过工作流。