anti-slop-pr-and-writinglisted

# Anti-slop PR and writing **Trigger.** You are writing or reviewing Pull Request descriptions, git commit messages, architecture documentation, or release notes. Also load whenever text has accumulated conversational filler, robotic clichés, superficial summaries, or sycophantic phrasing. > **Reference material** (the 20+ specific slop catalog, before-and-after tables, and diff cleaning patterns): see `reference.md`. ## The core doctrine > **Engineers read diffs to understand intent and mechanics. AI slop obscures intent, wastes review attention, and destroys credibility.** Good technical writing is dense, precise, and human. When editing with or through an agent, eliminate artificial mannerisms without flattening the author's voice or stripping technical context. ## Five patterns to strip on sight ### 1. Conversational sycophancy and robotic apologies - **Strip**: "Certainly!", "I would be delighted to help with that!", "As an AI language model...", "I apologize for the oversight." - **Replace with**: Direct statements of action, findings, or code changes. ### 2. Throat-clearing openers - **Strip**: Temporal clichés about fast-paced eras, "Here's the thing...", "Let's dive in...", "It goes without saying that..." - **Replace with**: The actual subject, problem, or decision in sentence one. ### 3. Binary contrasts and fake profundity - **Strip**: "It's not X. It's Y.", "The future isn't coming; it's already here.", "This changes everything." - **Replace with**: Conc