skill-creator

1## Activation Contract
2 
3Create a skill when:
4- A pattern is used repeatedly and AI needs guidance
5- Project-specific conventions differ from generic best practices
6- Complex workflows need step-by-step instructions
7- Decision trees help AI choose the right approach
8 
9Do not create a skill when the pattern is trivial, one-off, or better served by normal documentation.
10 
11## Hard Rules
12 
13- When working in this repo, first follow `docs/skill-style-guide.md` as the normative source before creating or updating skills.
14- For installed global skills, use `references/skill-style-guide.md` as the bundled local copy of that guide when `docs/skill-style-guide.md` is unavailable.
15- If neither guide is available, use the compact inline rules below.
16- A skill is a runtime instruction contract for an LLM, not human documentation.
17- Do not add a `Keywords` section; preserve essential trigger words in `description`.
18- References must point to local files.
19- Keep the skill body concise: target 180–450 tokens, recommended max 700, hard max 1000.
20 
21## Decision Gates
22 
23| Need | Action |
24|------|--------|
25| Code templates, schemas, fixtures, generated examples | Put them in `assets/` |
26| Conceptual detail, edge cases, existing docs | Put local links in `references/` |
27| Long explanation in `SKILL.md` | Move it to a supporting file |
28| Multiple meaningful paths | Add a compact decision table |
29 
30## Execution Steps
31…