write-plainlisted

> Source: [cursor/plugins - pstack/skills/unslop](https://github.com/cursor/plugins/blob/main/pstack/skills/unslop/SKILL.md). Adapted, not vendored verbatim; see "What this skill leaves out" below. The mechanical half of this policy is a hook, not a skill. `hooks/prose-gate.sh` blocks the word list, the filler phrases, the chatbot artifacts, curly quotes and emoji headings on every markdown write, commit message and PR body. Nothing in this file repeats that list. This skill covers what a regex cannot see. ## Process 1. Read the draft against the patterns below. 2. Rewrite. Keep the meaning, keep the register. 3. Ask what a reader does with each sentence. If a sentence supports no action, no decision, and no fact, cut it. ## Patterns ### Say what it does, not how it feels "The database stays close at hand", "SQL you can read", "types that follow your schema" all name a feeling. Name the mechanism or a number instead: "`.toSQL()` returns the exact string sent to the database", "a column rename fails the build". Two checks: - Restate the sentence as an instruction, a fact, or a number. If you cannot, cut it. - If the sentence could appear unchanged in another project's docs, it says nothing about this one. Cut it. ### Puffery and promotion "a pivotal moment", "a testament to", "the evolving landscape", "setting the stage for". Cut the frame, state what happened. Same for "nestled", "breathtaking", "groundbreaking", "renowned", "must-visit" in any description that sho