RulesPicked
Orwell’s 6 writing rules
Banning AI words one by one never ends: 6 rules from 1946 for your global rules file, plus prompts for docs, PRs and reports.
12K saves on X, as of Posted
Writing rules, from Orwell, 1946. These govern prose: docs, PR text, messages. Never touch code or technical terms; swap in everyday words only where precision survives.
1. Never use a metaphor, simile or other figure of speech which you are used to seeing in print.
2. Never use a long word where a short one will do.
3. If it is possible to cut a word out, always cut it out.
4. Never use the passive where you can use the active.
5. Never use a foreign phrase, a scientific word or a jargon word if you can think of an everyday English equivalent.
6. Break any of these rules sooner than say anything outright barbarous.
Review every prose output against these rules before delivering.Next Paste the rules into your global CLAUDE.md or AGENTS.md.
Stop telling Claude Code or Codex “no em dashes”, “stop saying delve” or “don’t sound like AI”. You never gave it a writing system. Every README, PR description and landing page ships in the same AI voice, and you ban words one at a time.
Orwell wrote the fix in 1946: six rules. Paste them into your global CLAUDE.md / AGENTS.md and every session picks them up. Global means it applies to every repo. Give one project its own voice with a project-level CLAUDE.md when you need to.
What it does to a sentence. Before: “Comprehensive error handling has been implemented across all API endpoints to ensure robust and reliable performance.” After: “We added error handling to every API endpoint.” Comprehensive, robust, reliable and ensure are gone, the passive turned active, and 16 words went down to 8 with the same facts.
Rewrite this text applying the six writing rules in CLAUDE.md. First list every violation: each stale phrase, each long word with its short replacement, each cuttable word, each passive construction. Then give the rewrite. Keep every fact, number and name unchanged.For every commit message and PR description: state what changed and why in plain words. No achievement language, no comprehensive, no robust. Apply the six writing rules before delivering. A reviewer should know what this does in one read.Rewrite this landing page copy under the six writing rules in CLAUDE.md. One concrete claim per line. Short words, active voice. Run the swap test on every line: if a competitor could paste it unchanged onto their page, rewrite it or delete it.Report progress in plain sentences: what changed, what failed, what comes next. No emoji checkmarks, no Successfully, no Perfect, no wall of bullets. Start with three lines; add detail only when it changes the next action.