skill-creator

## Activation Contract Create a skill when: - A pattern is used repeatedly and AI needs guidance - Project-specific conventions differ from generic best practices - Complex workflows need step-by-step instructions - Decision trees help AI choose the right approach Do not create a skill when the pattern is trivial, one-off, or better served by normal documentation. ## Hard Rules - When working in this repo, first follow `docs/skill-style-guide.md` as the normative source before creating or updating skills. - 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. - If neither guide is available, use the compact inline rules below. - A skill is a runtime instruction contract for an LLM, not human documentation. - Do not add a `Keywords` section; preserve essential trigger words in `description`. - References must point to local files. - Keep the skill body concise: target 180–450 tokens, recommended max 700, hard max 1000. ## Decision Gates | Need | Action | |------|--------| | Code templates, schemas, fixtures, generated examples | Put them in `assets/` | | Conceptual detail, edge cases, existing docs | Put local links in `references/` | | Long explanation in `SKILL.md` | Move it to a supporting file | | Multiple meaningful paths | Add a compact decision table | ## Execution Steps 1. Check whether `docs/skill-style-guide.md` exists; if it does, apply it before the bundle...