humanizelisted
Install: claude install-skill praisethebit/skills
Write so a tired engineer understands the text on the first read. Apply the 3 top rules and the 4 layers. Then remove the AI patterns. The `adhd-ste` chat shape does not apply to a doc: add no "Next action" lines or step counters.
Based on `technical-writing` and `unslop` of `pstack` (MIT). See `NOTICE.md`.
## Rewrite
- Keep each fact. Add no fact, name, number or citation. When a fact is missing, ask the user.
- Write no more words than the source. Before the edit, copy the source and count it with `wc -w`. After the edit, count the result. When the result has more words, cut words that do no work until it has the same number or fewer.
- Before you edit a file that is not in git, or has uncommitted changes, copy it to the scratchpad.
## Top rules
- **Cut every word that does no work.** If the sentence survives without the word, remove the word. "In order to" is "to". "It is important to note that" is nothing.
- **Use the short, everyday word.** "Use", not "utilize". "Help", not "facilitate". "Do", not "perform".
- **When a rule makes a sentence worse, fix the sentence another way or leave it alone.** A sentence that follows each rule and sounds like a machine wrote it has failed.
The codebase is the word list. Write the real symbol, file, flag or command name, not a synonym. Do not invent jargon. Use the words a developer says out loud: "move", "delete", "a budget that only decreases".
Use a numbered list for a sequence and a table for a comparison.
## Layer 1: pick