If a skill applies, youhave no choice, and must use it.
This is not a suggestion, but a hard rule. Don't act first and add the skill later.
How to obtain skills
In Claude Code: use theSkilltool. When you invoke a skill, its content will be loaded and presented to you - follow it directly. Never use the read tool on skill files.
In other environments: check your platform documentation to learn how to load skills.
Using skillsRules
Before any response or action, first invoke the relevant skill or the skill explicitly requested by name.
Even if a skill is only 1% likely to apply, invoke it to check first.
If after invoking it you confirm it does not apply, you may not use it; but you cannot skip the invocation step.
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 are rationalizing:
| Thought | Reality |
|---|---|
| "This is just a simple question" | A question is a task. Check skills. |
| "I need more context first" | Skill checks come before clarifying questions. |
| "Let me explore the codebase first" | The skill tells you how to explore. Check it first. |
| "I can quickly check git/files" | Files lack contextual context. Check skills. |
| "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 keep evolving. Read the current version. |
| "This doesn't count as a task" | Action = task. Check skills. |
| "The skill is overkill" | Simple things become complicated. Use it. |
| "I'll do one thing first" | Check before doing anything. |
| "This feels productive" | Undisciplined action wastes time. Skills prevent this. |
| "I know what this represents" | Understanding the concept ≠ using the skill. Invoke it. |
Skill priority
When multiple skills can be applied, use the following order:
- Process skills first(brainstorming, debugging) - these determine how to handle the task
- Implementation skills second(frontend design, mcp-builder) - these guide execution
"Let's do X" → brainstorm first, then implementation skills. "Fix this bug" → debug first, then domain-specific skills.
Skill types
Strict(TDD, debugging): follow strictly. Do not adapt the discipline.
Flexible(patterns): adapt the principles to the specific situation.
The skill itself will tell you which one.
User instructions
The description says "what to do", not "how to do it". "Add X" or "fix Y" does not mean skipping the workflow.