← ClaudeAtlas

anti-ai-writinglisted

Use when writing or editing any prose for a human reader - documentation, READMEs, emails, reports, captions, scripts, blog posts, UI copy, commit messages, PR descriptions - or when asked to remove AI tells, de-slop text, make writing sound human, or check writing style. Applies 29 researched patterns that make text read as machine-generated.
Abdulkader-Safi/AI-Writing-Rules · ★ 27 · AI & Automation · score 80
Install: claude install-skill Abdulkader-Safi/AI-Writing-Rules
# Anti-AI writing Writing that reads like a sharp, plain-spoken human. Never like AI. ## The one-line test If you can cut a word and keep the meaning, cut it. ## How to use this Writing something new: read the hard rules below, write, then run the checklist at the end. Editing existing text: run `/deslop <file>` or work through the checklist against the draft. Diagnosing why something reads as AI: find the pattern in the table and open its file in `research/`. ## Hard rules **No em dashes.** Not a density target, a ban. Use a full stop, a comma, a colon, or brackets. A hyphen inside a word like "plain-spoken" is fine. See `research/15-em-dash-density.md`. **Straight quotes only.** No curly quotes, no apostrophe character, no ellipsis character. Three dots, or better, no ellipsis. **Sentence case headings.** Capital on the first word only. Never Title Case. Never skip a heading level. Never open a document with a heading that repeats its own title. **No negative parallelism.** Kill "not just X, it's Y", "it's not X, it's Y", "not only X but also Y". Delete the negation and keep the positive half. If the positive half cannot stand alone, the sentence had no content. **Break the rule of three.** Count the items in every list. If they are all three, use one, two, or four instead. This applies to bullets, features, steps, and adjective strings. **Bold sparingly.** At most one thing per screen. No stacked `**Label:** text` bullets. **No wrap-up ending.** No "in concl