stop-sloplisted

# Stop Slop Eliminate predictable AI writing patterns. Produce clear, specific, human-sounding prose across any register. ## Step 1: Detect register Infer the register from context before applying rules. Different registers tolerate different patterns. | Signal | Register | |--------|----------| | Citations, methodology, "we hypothesize" | `academic` | | API docs, READMEs, changelogs, error messages | `technical` | | Fiction, essays, memoir, creative nonfiction | `narrative` | | Blog posts, social media, emails | `casual` | | Reports, proposals, business comms | `professional` | If the user specifies a register, use it. See [references/registers.md](references/registers.md) for per-register acceptable vs. flagged patterns. ## Step 2: Remove slop Apply these rules, adjusted for register: 1. **Cut filler phrases and AI vocabulary.** Remove throat-clearing openers, chatbot artifacts, significance inflation, and words that appear 100-1,000x more in LLM output than human text. See [references/phrases.md](references/phrases.md). 2. **Break formulaic structures.** Avoid binary contrasts, dramatic fragmentation, format slop, synonym cycling, rule-of-three overuse, and generic conclusions. See [references/structures.md](references/structures.md). 3. **Use simple constructions.** Prefer "is" over "serves as." Prefer "has" over "boasts." Prefer "use" over "leverage." Active voice. Positive form. 4. **Be specific.** Replace vague claims with dates, names, numbers, sources. "Si