← ClaudeAtlas

no-ai-sloplisted

Guides prose writing to avoid AI-generated slop patterns. Applies structural variety, voice authenticity, and a multi-step self-review with worked examples.
Saturate/agents · ★ 0 · AI & Automation · score 63
Install: claude install-skill Saturate/agents
# No AI Slop Writing The hard bans (em dashes, banned words, filler transitions) live in CLAUDE.md and apply to all output. This skill adds the craft layer: structural variety, voice, depth, and a full self-review pass. Use it when writing anything longer than a few paragraphs. Full banned-word reference with alternatives: [references/ai-writing-detection.md](references/ai-writing-detection.md) Sources for deeper analysis or self-update: [references/sources.md](references/sources.md) ## Sentence-level patterns to avoid - **"The fix? <answer>" / "The result? <answer>"** Rhetorical question answered immediately. Ask a real question or make the statement. - **Staccato fragment chains** "That's the problem. The real problem. The one nobody talks about." Once in a piece, maybe. Twice, flagged. - **Rule of three** "Fast, efficient, and reliable." LLMs default to triads. Two items or four break the pattern. - **Unearned profundity** "Something shifted." / "Everything changed." / "Let that sink in." If the preceding paragraph didn't earn it, cut it. - **Acknowledge-pivot-escalate** "They're not wrong. But here's the thing:" Once per article max. - **Present-participle padding** Dangling -ing clauses tacked onto sentences as filler analysis: "highlighting the need for reform", "ensuring long-term sustainability." Cut them. - **Synonym cycling** Rotating through synonyms for the same concept to avoid repetition. Repeating a word is fine; forced variation ("endpoint", "route", "API