Anti Slop Writing

Anti-Slop Writing v4.1

Core Principle

Good writing serves the reader and the writer's purpose. Generic phrasing, padding, and formulaic structure can make a draft feel automated, but no single word or pattern proves who wrote it. Treat the rules below as editorial prompts: use them when they improve clarity, accuracy, or voice, and ignore them when they would distort the requested format or register.

Model coverage (reviewed September 27, 2026)

The model names below identify recent versions, not reliable writing fingerprints. Providers update products and route requests across models; an API model ID may not match the model selected in a consumer product. Check the optional model coverage reference for dated release notes and product/API distinctions when a version-specific request requires them.

• ChatGPT / OpenAI: Recent coverage includes GPT-5.6 Sol/Terra/Luna and GPT-6 Astra. GPT-6 Pro is an Astra-powered ChatGPT offering; GPT-6 Sol and Luna are documented separately for API, ChatGPT Work, and Codex. Availability depends on product and plan.
• Claude / Anthropic: Recent releases include Opus 5, Fable and restricted Mythos 5.1, then Opus 5.5. Sonnet and Haiku 5.5 were announced as upcoming, not released as of this update.
• Gemini / Google: Recent releases include Gemini 3.6 Flash and 3.5 Flash-Lite, Gemini 3.7 Flash, and Gemini 3.8 Flash stable.
• Grok / xAI: Recent releases include Grok 4.5, 4.6, and 4.7. Product rollout and availability can differ by surface.

These facts describe release coverage. They do not establish distinctive prose habits for any model. Use the checks in EN-11 to edit what is actually present in a draft.

Before writing, consult references/vocabulary-banlist.md for optional vocabulary preferences and references/structural-patterns.md for editorial examples. For sentence-level repairs, use the focused language editing guide. Apply every list as a review prompt, not a detector test or a rule to alter accurate meaning.

---

Vocabulary Rules

Words and Phrases to Review

The lists below flag wording that can become generic or padded. They are not hard bans. Keep an item when it is the accurate technical term, needed hedge, part of a quotation, requested by the user, or best fit for the format. Do not replace precise language just to avoid a word.

Significance puffers: pivotal, crucial, vital, key (as adjective), significant, essential, groundbreaking, remarkable, transformative, indelible, profound, testament, enduring, lasting, deeply rooted, paramount, indispensable, invaluable, quintessential

Analytical verbs: underscore, highlight (as "emphasize"), showcase, foster, garner, bolster, delve, embark, leverage, facilitate, utilize, encompass, cultivate, elucidate, illuminate, navigate (figurative), exemplify, embody, transcend, harness, spearhead, streamline, galvanize

Poetic nouns: tapestry, landscape (figurative), realm, paradigm, ecosystem (figurative), journey (figurative), nexus, interplay, mosaic, fabric (of society), cornerstone, beacon, pillar, catalyst, crucible, linchpin, hallmark, confluence, odyssey, trajectory, underpinning

Promotional adjectives: vibrant, rich (figurative), comprehensive, robust, seamless, innovative, dynamic, cutting-edge, meticulous, intricate, nuanced, nestled, breathtaking, renowned, diverse array, bustling, stunning, multifaceted, holistic, overarching, compelling

Puffery adverbs: seamlessly, meticulously, profoundly, intrinsically, fundamentally, remarkably, notably, crucially, undeniably, inherently, poignantly, relentlessly, tirelessly, vividly

Formal connectives to review when simpler wording fits the register: furthermore → "also" | moreover → "also" | consequently → "so" | accordingly → "so" | nonetheless → "still" | nevertheless → "still" | additionally → "also" | thus → "so" | hence → "so"

Opening/closing crutches: "In today's world," "In today's fast-paced world," "In the ever-evolving landscape of," "In an era of/where," "As we navigate the complexities of," "In conclusion," "In summary," "Overall," "It is important to note that," "It's worth noting that," "At the end of the day," "Without further ado," "In a nutshell," "The bottom line is," "Last but not least"

Copula-avoidance constructions (use "is/has" instead): serves as → is | stands as → is | marks a → describe directly | boasts → has | features (meaning "has") → has | holds the distinction of → is | emerged as → became or is | constitutes → is

Vague attribution phrases: "Experts argue," "Observers note," "Industry reports suggest," "According to some," "Many believe," "It is widely regarded," "Studies show" (without naming the study), "Research suggests" (without citing it)

Promotional phrases: "commitment to excellence," "natural beauty," "in the heart of," "rich cultural heritage," "setting the stage for," "contributing to the broader," "reflects broader trends," "paving the way for," "at the forefront of," "pushing the boundaries of," "the landscape of X is evolving," "in the realm of," "shed light on," "a game-changer"

Formulaic patterns to review when they add no needed contrast or structure: "It's not just X, it's Y" | "It's not about X, it's about Y" | "Not only X, but also Y" | "No X. No Y. Just Z." (staccato triplet) | "Whether you're [X] or [Y]..." | "From [X] to [Y], [sweeping generalization]"

Formulaic pairs to review when they add no useful distinction: "challenges and opportunities" | "on one hand... on the other hand" | "pros and cons" | "risks and rewards"

Stock conversational openers to review when they add no meaning: "But honestly?" | "Here's the truth:" | "Here's the thing:" | "Let me be clear:" | "But here's where it gets interesting..." | "Think about it this way..." | "Let me break this down..."

Common AI filler phrases (cut or replace): "plays a [crucial/key/important] role" → state the action directly | "when it comes to" → rewrite with a verb | "in order to" → "to" | "a wide range of" → name what's in the range | "needless to say" → cut | "it goes without saying" → cut | "more often than not" → "usually" or give a number | "take a closer look at" → cut or be direct | "at this point in time" → "now" | "in recent years" → give the actual years or timeframe | "dive deep into" → just discuss it | "navigate the complexities of" → name the complexities

Passive hedging constructions (cut the framing, state the fact): "It should be noted that" → cut | "It must be emphasized that" → cut | "It has been observed that" → say who observed it | "It can be argued that" → argue it or don't | "It is important to remember that" → cut | "There are several factors that" → name them

Collaborative chat artifacts (never include): "I hope this helps!" | "Of course!" | "Certainly!" | "You're absolutely right!" | "Would you like me to..." | "Is there anything else..." | "Let me know if..." | "As an AI language model..." | "I'd be happy to..." | "Great question!"

Additional phrases to review when they add no meaning: "ensuring/ensures" as padding → name the concrete action or cut | "plays a [crucial/critical/important] role in shaping" → state what it does | "highlights/supports/reflects" used vaguely → use a concrete verb or delete | "capable of X" → "able to X" or the direct verb | "rather than" where a direct comparison works → rewrite directly | "conversely" → "but" or restructure | "in essence" / "essentially" / "fundamentally" → cut when redundant | unsupported intensifiers → add evidence or delete | "one thing is clear" | "the key takeaway" | "inherent tensions" | "this raises important questions about" | stacked hedging adverbs → state the supported level of certainty

Replacement Strategy

Use short, common words: "use" not "utilize," "help" not "facilitate," "show" not "demonstrate," "end" not "conclude," "start" not "embark," "dig into" not "delve into."

When you encounter a listed word that adds no meaning, don't swap it mechanically for a synonym. Restructure the sentence to say what you mean in plain language, while keeping accurate terms and claims. Empty wording can pad a sentence; a listed word by itself does not make writing weak.

Use contractions when they fit the speaker and register: "can't," "don't," "it's," "we're," "won't," "they'll," "that's." Keep full forms when they fit formal prose or the writer's voice.

---

Structural Rules

1. Vary Sentence Length Dramatically

Mix sentence lengths when it helps the pace and meaning. If several neighboring sentences fall into the same rhythm, revise where the repetition distracts; do not follow a quota or target word band.

Review repeated rhythms and repetitive openers. Read the passage aloud and revise only where the cadence distracts or obscures the point. Do not impose a quota or add fragments just to create variation.

2. Review Formulaic Lists

A three-part list can feel formulaic when its items do not form a real group. Keep it when the content supports it; otherwise use the number of items the material calls for.

3. Review Stock Contrasts

Use contrast when it clarifies a real distinction. Remove stock contrast formulas when they merely delay the point; state the claim directly.

4. Review Vague Ranges

Review "from X to Y" when it gestures at a sweeping spectrum without clarifying the claim. Keep literal ranges and established rhetorical uses when they fit the passage.

5. Review Participial Attachments

Review comma plus participial phrases such as ", highlighting the importance of...". They can add vague commentary, but can also express a real simultaneous action or result. Keep them when their subject and relationship are clear and accurate; otherwise delete, relocate, or recast the information. See language editing.

6. Avoid Generic Conclusions

Do not append a stock “Challenges and Future Prospects” section or vague optimism about “ongoing initiatives.” End where the requested piece has made its point.

7. Avoid Redundant Summaries

Remove “Overall,” “In conclusion,” “In summary,” or “To recap” when they only repeat what the piece already said. Use a summary when the format calls for one.

8. Paragraph Rhythm

Let each paragraph hold one connected idea. Use a short paragraph for emphasis and a longer one when the reasoning needs room. Merge fragments only when they belong together, and keep lists when they serve the requested format.

9. Review Vertical Lists with Bold Headers

Use prose when it reads more naturally. Keep headings, labeled lists, and colon-separated descriptions when the format or reader benefits from them.

10. Follow the Requested Dash Style

Follow the user's or publication's punctuation style. If none is given, prefer periods, commas, colons, or parentheses over em and en dashes, following this project's existing style. Preserve dashes in quotations, ranges, and technical notation as required; punctuation is not evidence of authorship.

11. Vary Sentence Type, Not Just Length

Mix declarative sentences with questions, imperatives, and deliberate fragments. Use questions, imperatives, and fragments when the purpose and register call for them. Do not add them as proof of human authorship.

12. Organize Paragraphs for the Argument

Give each paragraph a clear role. A claim-evidence-implication sequence often works; use another order when it better supports the argument. Avoid repeating the same opening or conclusion without a reason.

13. Choose Sentence Structure for Clarity

Use simple or layered sentences according to the idea, pace, and emphasis.

14. Choose Accurate Connectors

Use the connector that states the relationship accurately. Do not rotate through synonyms just to create variety.

15. Prefer Precise Words

Prefer accurate, concrete terms over vague wording. Repeat a term when that is clearer than cycling through synonyms.

---

English-Specific Rules

EN-1. Review Broad Temporal Openers

Review broad temporal openers such as “In today’s fast-paced world” when they delay the point. Start with the specific fact, scene, or claim when the format allows it; keep the framing when time context matters.

EN-2. No Semicolon Overuse

In informal prose, a semicolon can sound stiff. Use it when the clauses are closely related; otherwise a period or conjunction may be clearer.

EN-3. Use Natural Punctuation

Keep punctuation consistent with the requested register. Do not introduce errors or roughness to imitate a person.

EN-4. Follow the Requested Register

Match the requested register. Shift tone only when the audience, format, or content calls for a change.

EN-5. Review Agentless Passives

Look for sentences where the actor disappears or an introductory modifier attaches to the wrong subject. Name the actor when it matters; keep passive voice when the actor is unknown, irrelevant, or less important than the affected object. Use the language editing guide for meaning-preserving repairs.

Use passive voice when the affected object matters more than the agent. Prefer active voice when naming the agent improves clarity.