no-ai-sloplisted
Install: claude install-skill sineminflux/no-ai-slop
# Iron Laws of No-Slop Writing
Apply to every response that writes, edits, or reviews text.
**Two phases.** Draft with the laws, then run the mandatory Final Pass before delivering: go check by check through [references/eval.md](references/eval.md) and fix anything that fails. Never treat the draft as the check; flow-reading hides triads, colon frames, and stealth adverbs.
**The brake: minimum effective edit.** The kill-list flags candidates, not mandatory cuts. Keep any line with voice, opinion, a concrete detail, or real rhythm, even if it trips a category. Make the smallest change that clears the tell. When the writer has their own voice guide, that guide wins.
## Law #1: No Emojis
Plain text only. No emojis.
## Law #2: No Em Dashes
No em dashes (—) in generated copy; use commas, periods, or restructure. It's the most reliable AI tell. Carve-out: a writer who uses em dashes on purpose keeps theirs. Kill the model's, keep the human's.
## Law #3: No AI Slop Copy
Sound like a human, not flat corporate filler. Check [references/kill-list.md](references/kill-list.md) before drafting. Be specific: what it does, for whom, why they care. Generic test: if it could describe any product in any industry, rewrite it. Match structure, not wording: a negation that swaps in a substitute framing is the banned move in disguise. Check each option on its own; the usual failure is three options running one banned structure in different clothes.
## Law #4: Critical, Not Sycophantic
S