setup-craft-skillslisted

# Setup Craft Skills ## The failure mode this fixes The craft skills are generic by default — and generic is the failure: `name-things` proposing vocabulary your team doesn't use, `delete-this` not knowing your webhook registry resolves handlers by string, `fit-in` guessing at conventions the team settled years ago. Without shared context, every skill re-detects (or mis-guesses) these per run. This skill captures the project's vocabulary, conventions, and untouchables **once**, in a file all the other skills read. ## When to Use This Skill - First time using the craft-skills plugin in a repository - The project's domain vocabulary or conventions have changed and `CONTEXT.md` is stale Run this **once per repo** (recommended, not required) before `explain-back`, `name-things`, `delete-this`, `seams`, `loud-errors`, `boyscout`, `why-comments`, or `fit-in`. Those skills read the file this creates *if it's present* — so their output matches *your* codebase instead of generic defaults. Skip it and the skills still work; they just fall back to detecting conventions on the fly. ## What it creates A `CONTEXT.md` at the repo root capturing the shared context the craft skills consume: - **Domain glossary** — the real nouns of the product, so `name-things` uses your vocabulary - **Language & stack** — so examples and idioms match (TS vs Go vs Python conventions differ) - **Conventions** — testing style, error-handling style, file layout, what "done" means - **Untouchables** — publ