using-skills

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.

How to Access 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.

Using Skills

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.

Red Flags

These thoughts mean STOP—you're rationalizing:

Thought	Reality
"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 Priority

When multiple skills could apply, use this order:

1. Process skills first (brainstorming, recover-from-errors) - these determine HOW to approach the task
2. Implementation skills second (write-plan, execute-plan) - these guide execution
3. Verification skills last (review) - these confirm execution results

"Let's build X" → brainstorming first, then write-plan, then execute-plan, then review. "Fix this bug" → recover-from-errors if stuck, brainstorming if unclear.

Available Skills

Skill	When to Use
brainstorming	BEFORE any creative work: features, components, modifications
write-plan	After brainstorming, to create structured implementation plan
execute-plan	When you have a finalized plan file ready to implement
review	After plan execution completes, to verify all changes were implemented
recover-from-errors	After 2+ consecutive failures or when stuck

Skill Types

Rigid (execute-plan, recover-from-errors): Follow exactly. Don't adapt away discipline.

Flexible (brainstorming): Adapt principles to context.

The skill itself tells you which.

User Instructions

Instructions say WHAT, not HOW. "Add X" or "Fix Y" doesn't mean skip workflows.