Skill Router#

Core Directive: Before answering any user question, you MUST consult this skill first, check for matching specialized skills, and load them if found.

---

1. Skill Index#

This section is auto-generated by scripts/generate.py. Run python scripts/generate.py to update.

See the manual maintenance section below for alternatives.

---

2. Routing Rules#

Rule 1: Match & Load#

When the user's question matches any skill above, load it using the Skill tool. Load all matching skills — don't skip any.

Rule 2: Combined Loading#

Common combos:

• Code + Standards → Language-specific skill + coding-standards
• Deploy → deployment-patterns + canary-watch
• API Design → api-design + backend-patterns
• Frontend → frontend-design + frontend-patterns
• Writing → article-writing + brand-voice
• Tech Decision → blueprint + architecture-decision-records
• Code Walkthrough → code-tour + codebase-onboarding

General matching rules:

• When the user's question contains domain keywords, tech stack names, or terminology, load the matching skill
• One question may match multiple skills — load them all
• When in doubt, load one more rather than one less

---

3. Usage Report (Mandatory)#

After every task, you MUST report which skills were actually used at the end of your response.

text

---
**Skill Usage Report:**
- [skill-name] — [Status: Loaded / Not Triggered — Notes]

• List all matched skills with load status
• Also report when no skills were triggered
• This report MUST appear at the end of every response, never omit it.

---

Manual Maintenance#

If you prefer to maintain the index manually, place your content between <!-- SKILL_INDEX_START --> and <!-- SKILL_INDEX_END -->:

markdown

### Category
| Skill | Trigger |
|--------|----------|
| `skill-name` | Brief trigger condition description |
| `another-skill` | Another trigger description |

Index content can be in any format that helps the model match — keyword lists, tables, trigger phrases, etc.