craft-skilllisted

# Craft Skill > **HARD GATE** — Do NOT name a skill without a two-word verb-noun pair. Do NOT merge a new skill without running `sync-skills.sh` — the generated `.cursor/rules/` and `.gemini/` artifacts must match the source SKILL.md. ## Process 1. **Gather requirements** — ask user about: - What task/domain does the skill cover? - What specific use cases should it handle? - Does it need executable scripts or just instructions? - Any reference materials to include? - What specs/ output does it produce (if any)? 2. **Verify Principles** — Ensure the skill aligns with [PRINCIPLES.md](../docs/PRINCIPLES.md): - Is it atomic (verb-noun)? - Is it "deep" (simple interface, complex internal logic)? - Does it include Hard Gates? - Is it verifiable with a `.feature` file? 3. **Draft the skill** — create: - SKILL.md with concise instructions (see [REFERENCE.md](REFERENCE.md) for template) - Additional reference files if content exceeds 100 lines - Utility scripts if deterministic operations needed **Auto-skill from library README:** When user provides a library README or API docs URL, extract: triggers, HARD GATEs, verify commands, specs/ output — draft SKILL.md without inventing APIs not in the source. 4. Add `model:` frontmatter (`haiku` | `sonnet` | `opus`) per [model-profiles.md](../docs/references/model-profiles.md). > **STREAM CONTINUITY** — When writing file content, output in continuous chunks of ~200 lines. Do not pause. Continue i