← Back to Explore growing

Writing styleguide

Antislop-informed rules for keeping AI-assisted writing honest

February 2026

This is an internal reference for writing on this site. It combines two sources: empirical data from the Antislop paper (Paech et al., 2025) on statistically overused patterns in LLM output, and the voice patterns documented in our own voice analysis. One tells us what to avoid. The other tells us what to aim for.

The goal isn't sterile writing. It's aware writing. Know the patterns. Decide deliberately.


Part 1: What to watch for antislop

The Antislop paper analyzed creative writing output from 67 language models against human baselines (Reddit creative writing + Project Gutenberg). They measured how often specific words and phrases appear in LLM text relative to human text. The ratios are staggering — some patterns are over 1,000x more frequent in model output.

These aren't bad words. They're overused words. A human writer might use "flickered" once in a story. A language model reaches for it reflexively, across every story, because alignment training reinforced it as a safe, literary-sounding choice.

Word-level banlist

Top overrepresented words across 67 models. The "% models" column shows how many models have this word in their top 120 most overrepresented words relative to human writing.

word% modelsseverity
flickered / flicker / flickering98.5 / 94.0 / 92.5high
leaned82.1high
muttered82.1high
gaze80.6high
grinned80.6high
gestured77.6high
murmured73.1medium
nodded73.1medium
glint68.7medium
hesitated68.7medium
whispered68.7medium
blinked64.2medium
hummed64.2medium
faintly62.7medium
unreadable62.7medium
shimmered—high (2,882x in gemma-3-12b)
stammered—high (3,833x in gemma-3-12b)
unsettlingly—high (3,833x in gemma-3-12b)
containment77.6medium
addendum74.6medium

Context matters. "Flickered" in a story about a candle is fine. "Flickered" as the default verb for any light source in every story is slop. The question is always: did I choose this word, or did the model reach for its comfort zone?

Trigram banlist

Multi-word phrases that appear disproportionately in LLM output. These are the phrasings that make readers think "this sounds AI-generated" before they can articulate why.

phrase% models
voice barely whisper68.7
said voice low61.2
air thick scent / air thick smell49.3 / 19.4
took deep breath / take deep breath44.8 / 32.8
smile playing lips43.3
something else something / something else entirely37.3 / 26.9
could shake feeling31.3
eyes never leaving29.9
casting long shadows / long shadows across28.4 / 19.4
heart pounding chest25.4
spreading across face22.4

Structural patterns

Beyond individual words and phrases, models overuse certain sentence constructions.

"It's not X, it's Y" — 6.3x more prevalent than in human writing. The paper built regex patterns to detect and suppress this entire family. Variants: "It wasn't X, it was Y", "This isn't X, it's Y", "That's not X, it's Y", "not just X, but Y", "X isn't Y — it's Z". The construction itself isn't banned — sometimes it earns its place. But if you find three in one article, the model was driving.
Sensory clichés — "Air thick with [scent/tension/silence]", "voice barely above a whisper", "heart pounding in [chest/ears]", "eyes never leaving". These create an atmosphere that reads as template rather than observation.
Character name fixation — Models gravitate toward specific names. "Elara" appeared 85,513x more often in gemma-3-12b output than in human text. "Kael" shows similar patterns. If your AI collaborator suggests a character name, check whether it's a genuine suggestion or a default.
Generic intensifiers — "a profound sense of", "a deep sense of", "felt a surge of". These are the model reaching for emotional weight without earning it. If you can replace the phrase with "felt [emotion]" and lose nothing, it was padding.

Part 2: What to aim for voice analysis

From the voice analysis — patterns extracted from five years of raw journal entries. These are the things that make writing sound like a person, not a model.

Rhythm

Staccato → Reflection → Staccato
Short punch. Short punch. Longer flowing thought that develops the idea. Short punch.
Fragment punches — Short declarative fragments that hit hard. No subject needed. "Let's get to work." "Make shit up. Make it real."
Breathing separators — Use whitespace to mark thought boundaries. Let ideas stand alone without forcing connections.

Tone

Direct profanity — When frustrated or emphatic. Never gratuitous. Punctuation, not filler.
Self-questioning — Mid-thought interrogation. Questions that drive exploration and signal genuine uncertainty.
Rhetorical escalation — Questions that answer themselves through absurdity.
Parenthetical asides — Process thinking made visible. Shows the work.

Transformation rules

When going from draft to published:

Preserve

  • Fragment punches
  • Profanity when earned
  • Self-questioning
  • The earnest plea ("Please.")
  • Parenthetical asides
  • Meta-awareness
  • Specific numbers and timestamps

Avoid

  • Over-explaining (trust the reader)
  • Softening profanity
  • Removing questions
  • Excessive formality
  • AI superlatives ("Absolutely!", "Great question!")
  • Hedging ("It could be argued...")
  • Bullet-point spam

Part 3: The editing pass synthesis

Where the two sources meet. Antislop tells us what patterns to scan for. The voice analysis tells us what to replace them with. Neither is sufficient alone — you can strip all the slop words and still end up with generic text if you don't know what voice to aim for.

Editing checklist

  1. Word scan — Search for banlist words. For each hit: did I choose this, or did the model? If the model, replace or cut.
  2. Phrase scan — Search for trigram patterns. These are harder to spot because they sound "literary." That's the trap.
  3. Structure check — Count "It's not X, it's Y" constructions. One per article might be fine. Three means the model was driving.
  4. Rhythm check — Read it aloud. Does it follow staccato-reflection-staccato? Or does every paragraph drone at the same length?
  5. Voice check — Does this sound like a person wrote it? Would you say this out loud? If it sounds like a LinkedIn post, rewrite.
  6. Hedging check — Cut "perhaps", "it could be argued", "one might say". State things or question them. Don't hedge.

The tension

Over-policing kills voice too. The antislop paper itself makes this point — hard bans on vocabulary cause worse problems than the slop they prevent. Their solution was "soft bans": reduce the probability of overused patterns without eliminating them entirely.

Same principle applies to manual editing. If "whispered" is genuinely the right word, use it. The goal is to notice when the model is on autopilot, not to avoid every word on a list. Awareness over avoidance.


Quick reference

SCAN FOR: - Banlist words (flickered, gaze, murmured, whispered, nodded...) - Banlist trigrams (voice barely, air thick, took deep breath...) - "It's not X, it's Y" constructions - Generic intensifiers (profound sense, deep sense, surge of) - Sensory clichés (casting long shadows, heart pounding) AIM FOR: - Fragment punches for emphasis - Self-questioning where uncertain - Staccato → reflection → staccato rhythm - Profanity as punctuation, not filler - Specific details over generic atmosphere PRINCIPLES: - Did I choose this, or did the model? - Awareness over avoidance - Soft bans, not hard bans - Preserve the weird parts — they're yours