When to Use Which Skill

Choosing the right Skill for the task is key to efficiency.

By Task Type

Task	Skill	Why
Unknown bug	`diagnose`	Systematic debugging
Fix known cause	`tdd`	Test-first fix
Performance regression	`diagnose`	Performance analysis
Security vulnerability	`security-review`	Dedicated security audit

Code Quality

Task	Skill	Why
Pre-PR review	`review`	General code review
Security audit	`security-review`	OWASP Top 10 check
Remove duplication	`simplify`	Micro-simplification
Architecture issues	`improve-codebase-architecture`	Macro-level improvement

Dev Workflow

Task	Skill	Why
New feature	`tdd`	Test-driven quality
Quick validation	`prototype`	Throwaway prototype
Design review	`grill-me` → `prototype`	Grill then validate

Project Management

Task	Skill	Why
Issue triage	`triage`	State-machine triage
Document requirements	`to-prd`	Structured PRD generation
Break down work	`to-issues`	Vertical slice breakdown
Hand off work	`handoff`	Session handoff docs

Config & Tools

Task	Skill	Why
Init project	`init`	Generate CLAUDE.md
Config permissions	`update-config`	Configuration management
Reduce prompts	`fewer-permission-prompts`	Permission analysis
Create Skill	`write-a-skill`	Skill creation guidance
Custom keybindings	`keybindings-help`	Shortcut config
API development	`claude-api`	Claude API specialist

Productivity

Task	Skill	Why
Save context	`caveman`	75% token reduction
Periodic checks	`loop`	Auto-recurring execution
Stress-test plan	`grill-me`	Systematic interrogation
Review against docs	`grill-with-docs`	Doc alignment

Common Workflows

Workflow 1: Idea to Code

grill-me → prototype → to-prd → to-issues → tdd → review → simplify

Workflow 2: Bug Fix

triage → diagnose → tdd(add tests) → review

Workflow 3: Code Review

review → simplify → security-review(optional)

Workflow 4: Onboarding

init → understand-anything:understand-onboard → grill-with-docs

Selection Principles

One Skill per problem — Don't activate conflicting Skills simultaneously
Diagnose first — When unsure, start with diagnose
Prototype early — Validate approach with prototype before building
Review habitually — review after every change