ijfw-writing-skills

# IJFW Writing Skills -- author a new skill correctly A skill is a thin loadable trigger surface. The `description:` is what Claude reads to decide whether to hot-load the body. Get the description wrong and the skill never fires; get the body wrong and the skill misfires when it does fire. This file teaches you to do both right on the first try. **Iron rule:** a skill IS its trigger. If the description does not match the words a user would naturally say, the skill does not exist -- it is documentation no one reads. --- ## 1. Discovery -- the description is the trigger surface (CSO) The `description:` field is the only thing Claude sees at routing time. Treat it like a search-engine snippet, not like a definition. **Shape:** start with "Use when ...", end with `Trigger: <verbatim phrases>, /<command-name>`. **Forbidden words** (enforced by `scripts/lint/check-skill-descriptions.sh`, case-insensitive whole-word): `step`, `steps`, `phase`, `phases`, `mode`, `modes`, `workflow`, `stage`, `process`, `sub-skill`, `skill-name`. These signal "the description summarises the body" and cause Claude to skip the body and follow the description shortcut. **Hard cap:** 1024 characters. Aim for under 300. ```yaml # BAD -- defines the topic, uses forbidden word "process" description: "Skill for the code review process. Reviews PRs." # BAD -- workflow summary, uses "phases" and "steps" description: "Use when reviewing code -- runs three phases, fifteen steps, two passes." # GOOD --...