agent-writinglisted
Install: claude install-skill ychampion/ystack
# Agent writing
An agent reads every word, every time, and acts on what is concrete. Vague text costs tokens on every
run and still gets ignored. Write less, and make each line something the agent can do or check.
## When it applies
- Writing or editing a skill, a CLAUDE.md / AGENTS.md, a system prompt, or a brief for another agent.
- An agent keeps skipping a rule: the wording is usually the bug.
## Skills
- **Name:** short, lowercase, hyphenated, a verb or a noun the user would say.
- **Description is the trigger.** It is always loaded; the body loads only when it fires. Write what
the skill does in one sentence, then "Use for/when" with the phrases a user really types and the
situations that should fire it. One phrase per distinct case; drop synonyms.
- **Body:** when it applies (and when to skip), the procedure as numbered steps, rules, output format.
Each step ends on something checkable.
- **Budget:** 40-150 lines. Push rare branches and long reference into a sibling file, named from the
step that needs it ("for X, read `ref/x.md`").
## Rule files (CLAUDE.md, AGENTS.md)
- Every line costs on every turn. Keep only rules the agent would get wrong without them.
- Each rule: the instruction, then a short why. The why lets the agent handle cases you didn't list.
- Put the exact command, path or pattern in the rule. "Use bun" beats "prefer our package manager".
- Move anything used rarely into a referenced file with a trigger line.
## Briefs to another agent