erikpr1994 Using Skills
The Rule
Invoke relevant skills BEFORE any response or action.
User message received
|
v
Might any skill apply? (even 1% chance)
|
+--> YES --> Invoke Skill tool --> Follow skill instructions
|
+--> NO --> Respond directly
How to Access Skills
In Claude Code: Use the Skill tool. When you invoke a skill, its content is loaded for you to follow.
Never use the Read tool on skill files. Always use the Skill tool.
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 handle this quickly" | Speed without skills = missed protocols. |
| "This doesn't need a formal skill" | If a skill exists, use it. |
| "I remember this skill" | Skills evolve. Read current version. |
| "The skill is overkill" | Simple things become complex. Use it. |
| "I'll just do this one thing first" | Check BEFORE doing anything. |
Skill Priority
When multiple skills could apply:
- Process skills first (TDD, debugging, brainstorming) - determine HOW to approach
- Domain skills second (git, infra, frontend) - provide specific guidance
Examples:
- "Let's build X" -> brainstorming first, then implementation skills
- "Fix this bug" -> debug first, then domain skills
- "Implement feature Y" -> TDD skill, then relevant domain skills
Skill Types
Rigid (TDD, debugging): Follow exactly. Don't adapt away discipline.
Flexible (patterns, domain): Adapt principles to context.
The skill content tells you which.
Core Skills
| Skill | When to Use |
|---|---|
| session | Multi-step implementations, features, refactoring |
| test-driven-development | Any code that needs tests (most code) |
| debug | Errors, bugs, things not working |
| git-expert | Commits, branches, PRs, version control |
| codebase-navigation | Finding files, understanding structure |
| documentation-research | Looking up library docs, APIs |
Session Workflow
Most significant work follows this pattern:
- Load relevant skills
- Create/update session file (.claude/tasks/session-*.md)
- Execute with skill guidance
- Commit with proper format
- Update session status