← Back to Blog

How to Remove AI Slop From Fiction: Fix the Shapes

How to Remove AI Slop From Fiction: Fix the Shapes

You did the obvious thing first. You searched the chapter for delve, tapestry, testament, a symphony of, and you killed every one of them. You swapped the three "sardonic smiles" for nothing at all. Then you read the chapter again, start to finish, and it still smelled. Not of any one word. Of the whole thing: the way every paragraph landed on the same note, the way your narrator kept explaining a moment that had already happened in front of you.

That's because AI slop in fiction isn't mostly a vocabulary problem. It's a structural one. The words are the skin; the tells that readers actually clock live in the skeleton: sentence shapes the model reaches for again and again, regardless of which words fill them. This guide is about finding those shapes and taking them apart, one revision pass at a time.

Why deleting "AI words" doesn't fix AI prose

Banned-word lists remove the most quotable tells but leave the patterns that make prose read as generated: repeated sentence templates, explained beats, and a flat rhythm. You can strip every delve from a chapter and a reader will still feel the machine, because they're responding to shape, not diction.

One r/WritingWithAI poster put it exactly: they could remove words like delve or seamless and the draft "can still feel very obviously generated," because what they noticed now was the structure: "X isn't about this. It's about that." Then the same sentence shape again and again, with different words. They also flagged the habit of "explaining a point after the example already made it clear."

Here's the line worth remembering: slop is a shape, not a vocabulary. A word list catches a word. It can't catch a template, because the template survives any substitution you make inside it.

There's a second reason word lists disappoint, and a commenter in the widely shared Deslopping Claude prose thread named it: a lot of these tics "are parts of good writing that claude overdoes." Staccato sentences work when used sparingly. Specific is sometimes the right word. Ban it outright and you get strange sentences instead of good ones. The fix isn't prohibition. It's frequency control, and frequency is something you can only see when you read for structure.

The five structural tells (and what each one sounds like)

The tells that survive a word purge are: the negation pivot, the hypothetical comparison, the rule of three, the explained beat, and uniform rhythm. Each has a recognizable silhouette, and once you've seen it you'll find it on every page.

1. The negation pivot: "It wasn't X. It was Y."

It wasn't anger in his voice. It was something older, something closer to grief.

The model defines what a thing is by first naming what it isn't, which manufactures a tiny reversal in every paragraph. Its cousin is the triple negation: Not out of fear. Not out of duty. But because she had nowhere else to go. Once per book, it can hit. Nine times per chapter, it's a metronome.

2. The hypothetical comparison: "the way a… the kind that…"

She held the cup the way a woman holds something she's afraid to set down. It was the kind of quiet that settles after a door closes.

A poster in an r/WritingWithAI thread about Opus 4.6 singled out exactly this, "the way a... the kind that...", noting it "doesn't really make sense as an internal monologue." That's the craft problem in a nutshell. Real people in a moment of stress don't compare their surroundings to a hypothetical version of those surroundings. They notice one thing. The construction invents a third party (some woman, some door, some other quiet) and describes your character through them. It reads as insight and delivers distance.

3. The rule of three

The kitchen smelled of burnt sugar, old coffee, and something she couldn't name.

Three adjectives, three verbs, three sensory details, with the third usually vaguer than the first two. Humans use triplets too, just not in every paragraph.

4. The explained beat

Marcus set the ring on the table and walked out without a word. He was done, and they both knew it.

The first sentence did the work. The second sentence explains the first sentence to a reader the model assumes wasn't paying attention. This is the most damaging tell of the five because it doesn't just sound generated; it kills subtext. If you've read our piece on why AI dialogue comes out on the nose, this is the narration-level version of the same reflex.

5. Uniform rhythm

Read a generated chapter aloud. Paragraphs of near-identical length, sentences clustered between twelve and twenty words, a dramatic one-line paragraph every few hundred words, right on schedule. No single sentence is wrong, but the cadence never changes, and readers feel that before they can name it.

A worked chapter: what the shape pass actually finds

In practice, a structural pass cuts more than a word pass and changes how the chapter reads, because it removes whole sentences rather than swapping words. Here's what that looks like on a real-sized chapter.

Say you're Ines, three books into a cozy mystery series about a ferry-terminal café owner. Chapter seven of book four came back from the model at 3,100 words: Ines's sleuth, Dot, finds a forged timetable in the lost-and-found box and confronts the night clerk. Ines runs her word list first. Twenty-two hits: two tapestries, a testament, a cluster of quietly. She fixes all of them in twenty minutes. The chapter still reads like a chapter nobody wrote.

So she does the shape pass. She reads only for the five silhouettes, marking each with a letter in the margin. The count, when she's done: eleven negation pivots, seven "the way a / the kind of" comparisons, fourteen triplets, and, the one that stings, nineteen sentences that explain something the previous sentence had already shown. Dot slams the timetable on the counter, and then the narration tells us she's angry. The clerk's hand shakes, and then the narration tells us he's lying.

Ines deletes the nineteen explanations outright, stitching only the grammar. That alone takes the chapter to about 2,750 words. She keeps three of the eleven negation pivots (the ones attached to genuine reversals, where Dot really did expect one thing and find another) and turns the other eight into plain statements. Four of the seven hypothetical comparisons become one concrete thing Dot notices: not "the kind of silence that follows a lie" but the clerk's thumb working at a chip in the counter laminate. The triplets she thins by cutting the vague third item every time.

Final count: 2,640 words, one evening's work. The plot didn't change, and Dot's voice got stronger, because she now notices things instead of narrating her feelings about them. That's the trade: cut the second explanation, keep the first evidence.

How to de-slop AI fiction: a five-pass revision method

Run five short passes, each hunting one structural tell, in this order: explained beats, negation pivots, hypothetical comparisons, triplets, rhythm. Order matters, because cutting explained beats first removes text you'd otherwise waste time polishing.

  1. Cut the explained beats. Read each paragraph's last sentence and ask: did the action or dialogue already make this clear? If yes, delete it. Don't rephrase it, don't soften it. One commenter in the deslopping thread offered an editor prompt built on exactly this rule: "never replace deleted material with a cleaner version of the same beat." That's good advice for a human pass, too.

  2. Ration the negation pivots. Search for wasn't, not, isn't, and but near the start of sentences. For each pivot, ask whether the character genuinely expected the first thing. If not, state the second thing plainly. Keep one in five, at most, and only where the reversal is real.

  3. Replace hypotheticals with one observed detail. Every "the way a…" or "the kind of…" becomes a single concrete object or action your POV character would actually register. A gruff dockhand doesn't think the fog moved "the way grief moves through a house." He thinks the fog's got the far bollards.

  4. Break the triplets. Cut the third item, usually the vague one. If all three items are strong, keep two and move the third to a different sentence. You're not banning lists; you're breaking the habit of every list being exactly three long.

  5. Read aloud for rhythm. This is the only pass you can't do with search. Read the scene out loud and mark every place you fall into a sing-song. Then vary it on purpose: merge two medium sentences into one long one, chop a long one into a fragment, let a paragraph run long when a character is spiraling. Rhythm problems are often voice problems in disguise, and the fixes overlap heavily with making each character sound like themselves.

If a model does the first four passes, give it one narrow instruction per pass, not a single "remove the slop" prompt. Do pass five yourself.

Stopping slop at the draft stage instead of the edit

You'll still revise, but you can cut the volume of tells by giving the model exact phrase bans and a sample paragraph in your voice before it writes. Vague instructions like "avoid clichés" don't work; specific ones do.

The most practical advice in that Opus 4.6 thread came from a commenter who keeps "a short blacklist of exact phrases" in their instructions and adds to it whenever something grates, noting that models "respect specific bans surprisingly well, way better than 'avoid slop', which is too vague to act on." They paired it with a second move: set the narration register explicitly (he notices things, he doesn't analyze them) and paste a short paragraph of narration in the target voice, because "one good example beats ten instructions every time."

A few concrete habits:

  • Ban shapes by example, not by name. "Don't use negation pivots" is abstract. "Never write sentences like It wasn't fear. It was resignation." gives the model a pattern to match against.
  • Keep the ban list short and living. Ten entries you actually see in your drafts beat a hundred scraped from the internet.
  • Generate in smaller beats. A model asked for a whole 3,000-word scene fills the space with summary and explanation. Ask for one beat at a time and there's less room to pad.
  • Edit with a different model than you drafted with. Both the original poster and a commenter in the deslopping thread recommend this, since each model has its own tells and a second model is more likely to notice the first one's habits. This is one place a model-agnostic setup pays off: in NovelMage, you can draft with Claude through your own API key and run the edit pass on a local model through Ollama or LM Studio, without copying chapters between browser tabs.

Draft-stage prevention also connects to the deeper "flatness" problem. Many explained beats come from the model writing at a distance from the character, and if that's what you're fighting, our guide to the deep POV fix for flat AI prose goes further.

Frequently Asked Questions

What is AI slop in fiction?

AI slop in fiction is prose that reads as unedited model output. The obvious signs are overused words like tapestry or testament, but the more persistent signs are structural: repeated sentence templates such as "It wasn't X, it was Y," hypothetical comparisons ("the way a…"), constant triplets, sentences that explain what the scene already showed, and a monotonous rhythm.

Can I just tell the AI not to write slop?

General instructions like "avoid slop" or "avoid clichés" rarely change much, because they're too vague to act on. Specific bans work far better: quote the exact constructions you never want, keep the list short, and paste a sample paragraph of narration in your target voice. Expect fewer tells, not zero. You'll still need a revision pass.

Should I still use a banned-words list?

Yes, as a fast first pass, not as the whole job. A word list catches the most recognizable tells in minutes but misses sentence shapes entirely, and blanket bans on useful words like specific or rhythm produce awkward sentences. Use the list to direct your attention, then decide case by case.

The short version

De-slopping isn't a search-and-replace job. It's reading for shape: cut the explained beats, ration the pivots, swap hypotheticals for one real detail, break the triplets, and read the whole thing aloud. Do that, and the vocabulary mostly takes care of itself. One honest limit: these passes won't give you a voice you don't have. They clear the model's defaults out of the way so yours can come through.

If you want to draft with one model and edit with another while your manuscript stays on your own machine, NovelMage is a desktop app for Windows and macOS that runs local models via Ollama or LM Studio, or your own Claude, GPT, or Gemini keys, for a one-time $99.99. See what the lifetime license includes.

Share this article

Loading comments...