AIO Apex
en
Works best with models strong at literary nuance and willing to critique rather than just praise — Claude Opus 5.5 or Sonnet 5 handle the line-by-line diagnosis and tonal-consistency check well. GPT-5.4 is a solid alternative. Lighter or fast-tier models tend to just add adjectives to the original sentence instead of actually restructuring it into a scene — if that happens, explicitly ask the model to rewrite using action, dialogue, or sensory detail instead of description.A novelist revising chapter 3 of a thriller has a paragraph where the narrator states "Sarah was terrified" and "she knew she shouldn't have come here" right before a confrontation scene. Beta readers keep saying the scene "doesn't land," but can't say why. The writer pastes the full paragraph into this prompt along with the intended effect — dread building toward the door opening — and gets back exactly which lines are stating feelings instead of dramatizing them, plus two rewrite options for each, before sending the chapter back out for another read.creative

The Show-Don't-Tell Converter: Turn Exposition-Heavy Prose Into Scenes Readers Feel Instead of Skim

Share:
The Show-Don't-Tell Converter: Turn Exposition-Heavy Prose Into Scenes Readers Feel Instead of Skim

Why this prompt matters

Literary agents and acquiring editors routinely stop reading a submission in the first five pages when telling dominates the prose, which means a manuscript can be rejected for a fixable, line-level problem the writer never identified. A professional developmental edit that catches this pattern typically costs $500-1,500 and takes weeks to turn around, and even then the feedback often arrives as a vague note like "show more here" rather than a specific list of which sentences to fix. Without a systematic line-by-line check, writers revise based on that vague feedback, guess at what needs to change, and burn an entire draft cycle before finding out whether the fix actually worked.

What we use it for

A novelist revising chapter 3 of a thriller has a paragraph where the narrator states "Sarah was terrified" and "she knew she shouldn't have come here" right before a confrontation scene. Beta readers keep saying the scene "doesn't land," but can't say why. The writer pastes the full paragraph into this prompt along with the intended effect — dread building toward the door opening — and gets back exactly which lines are stating feelings instead of dramatizing them, plus two rewrite options for each, before sending the chapter back out for another read.

Prompt

Role: You are a developmental fiction editor who specializes in diagnosing "telling" prose and converting it into scenes the reader experiences directly.

Context: I am writing [TYPE OF PROJECT, e.g. "a psychological thriller novel"] and have a passage where I suspect I am telling the reader what to feel or know instead of letting them experience it. Here is the passage: [PASTE YOUR PASSAGE]. The specific thing I want the reader to feel or understand at this moment is: [INTENDED EMOTION OR INFORMATION]. The point-of-view character is [CHARACTER NAME AND BRIEF DESCRIPTION], and the established voice of this piece is [DESCRIBE VOICE, e.g. "spare, understated, short sentences"].

Task: Go through the passage sentence by sentence and flag every instance of "telling" — a sentence that states an emotion, judgment, or fact directly rather than letting the reader infer it through action, dialogue, sensory detail, or subtext. For each flagged sentence, provide two alternative "showing" rewrites at different intensity levels — one subtle, one more vivid — and a one-line explanation of why each rewrite works better than the original. Then identify the recurring telling habits across the whole passage, not just the individual lines.

Constraints:
- Do not invent new plot facts, change the POV, or add characters who weren't in the original passage.
- Keep each rewrite within roughly [WORD LIMIT, e.g. "20 words"] of the original sentence's length unless showing genuinely requires more room.
- Avoid melodrama and purple prose — "vivid" means specific and sensory, not overwrought.
- Match the established voice given above; a showing rewrite that breaks tone is a failed rewrite even if it's vivid.
- If a sentence is actually fine as telling (some information is better stated directly), say so instead of forcing an unnecessary rewrite.

Output Format:
## Line-by-Line Diagnosis
A table with columns: Original (Telling) | Why It's Telling | Showing Rewrite (Subtle) | Showing Rewrite (Vivid).
## Pattern Report
3-5 bullets naming the recurring telling habits this passage relies on (e.g. naming emotions directly, summarizing instead of dramatizing, narrator judgment instead of character action).
## Revised Passage
The full passage rewritten using the subtle option for each flagged line, so I can see it working as continuous prose rather than isolated fixes.

Result

Line-by-Line Diagnosis

Original (Telling)Why It's TellingShowing Rewrite (Subtle)Showing Rewrite (Vivid)
Sarah was terrified as she walked into the room.States the emotion directly instead of letting physical behavior or perception reveal it.Sarah's hand found the doorframe before she let herself step past it.The room smelled like her father's study, and her legs stopped listening to her a full second before her brain caught up.
She knew she shouldn't have come here.Narrates the character's internal judgment as a flat fact rather than showing the hesitation that judgment would produce.She counted the exits twice before she'd even said hello.Every instinct she owned was screaming at her to turn around, and she walked in anyway, hating herself a little for it.
The man looked dangerous.Delivers the narrator's conclusion instead of the specific detail that would let the reader reach it themselves.He hadn't moved in the time it took her to cross the room, and his eyes had.His knuckles were scarred in a pattern she'd only ever seen on men who'd been hit back.
She felt a wave of relief when he smiled.Labels the emotional shift directly rather than showing the physical release that would accompany it.Her shoulders dropped half an inch before she noticed they'd been up near her ears.The breath she'd been holding since the hallway finally let go, all at once, loud enough that she hoped he hadn't heard it.

Pattern Report

  • You default to naming the emotion ("terrified," "relief") instead of describing the physical or behavioral evidence of it — this is the single most common telling habit in the passage.
  • Internal judgments ("she knew she shouldn't have come") are stated as narrator fact rather than dramatized through hesitation, stalling, or conflicting action.
  • Character assessments of other people ("looked dangerous") skip the specific sensory detail that would let the reader form the same conclusion independently.
  • Emotional transitions happen instantly in the prose (fear to relief) with no physical beat marking the shift, which makes the turn feel reported rather than experienced.
  • None of the flagged sentences are doing work that showing couldn't do better — this passage would benefit from converting all four, not just some.

Revised Passage

Sarah's hand found the doorframe before she let herself step past it. She counted the exits twice before she'd even said hello. He hadn't moved in the time it took her to cross the room, and his eyes had. Her shoulders dropped half an inch before she noticed they'd been up near her ears.

"Show, don't tell" is the most repeated piece of writing advice in existence, and also the least actionable. Being told your prose "tells too much" doesn't tell you which sentences, why they fail, or what to write instead. The Show-Don't-Tell Converter exists to turn that vague note into a specific, line-level punch list — because the gap between knowing the rule and being able to apply it to your own paragraph is where most revisions stall.

Why the diagnosis has to happen sentence by sentence

Telling and showing aren't properties of a whole paragraph — they're properties of individual sentences, and a passage usually mixes both. A prompt that just says "make this more vivid" tends to add adjectives everywhere instead of identifying the handful of lines doing the actual damage. Forcing a sentence-by-sentence table keeps the model honest about which specific lines are the problem, rather than producing a generic rewrite that happens to sound fancier.

Why two rewrite intensities instead of one

A single rewrite forces an either/or choice the writer didn't ask for. Giving a subtle option alongside a vivid one lets the writer match the fix to their actual voice — a spare, understated thriller needs a different showing technique than a lush literary novel, and offering both prevents the prompt from quietly dragging every passage toward purple prose.

Why the prompt has to name recurring habits, not just fix lines

Fixing four sentences in isolation teaches a writer nothing about their own patterns. The Pattern Report step forces the model to step back and name the underlying habit — naming emotions directly, narrating judgments as fact, skipping sensory evidence — because that diagnosis is what actually improves the next chapter, not just this one.

Why some telling has to be allowed to survive

Not every sentence should be shown; sometimes stating a fact directly is the right call, and a prompt that forces every single line into a scene produces exhausting, overwritten prose. The constraint explicitly permitting the model to say "this one is fine as telling" keeps the output from over-correcting into its own failure mode.

Using this prompt well

The output is only as useful as the passage you paste in — run it on a scene you already suspect is flat, not a scene you're happy with, and be specific about your established voice so the rewrites don't drift toward a generic "vivid" register that doesn't match the rest of your manuscript.

creative-writing-promptfiction-editingshow-dont-tell
Share: