AI-generated dialogue where every character sounds like a slightly different version of the same narrator is a Claude AI skill — and why that's a structural issue, not a quality one.
You've seen it. You've probably produced it without meaning to. A scene between two people where the dialogue is technically correct — the conflict is there, the beats land, the pacing is fine — and yet when you read it back, something is wrong. Both characters sound like they were written by the same person with the same vocabulary making the same rhetorical choices. Because they were.
That's not a Claude problem. That's a context problem. AI generates dialogue the way it generates everything else: from the statistical shape of what it's seen before. And what it's seen before is thousands of generic scenes where characters serve plot functions rather than exist as specific people. Give it a scene setup with no character psychology, and it produces the most probable version of that scene — which is exactly what everybody else's AI-generated script also looks like.
The failure isn't in the output. It's in what doesn't go into the request.
The Three Things Generic AI Never Knows Before It Writes
Most people prompt AI dialogue the same way: describe the scene, maybe name the characters, sometimes describe what needs to happen. Then ask it to write. That approach skips three things that determine whether dialogue sounds like a real person or a plot delivery mechanism.
Generic AI writes characters as plot functions. It moves them through the scene efficiently. It doesn't know — and can't infer — who they are underneath the scene's surface objective.
That gap is exactly what the Dialogue Character Film Prompt skill for Claude was built to close.
What "Sounds Like a Real Character" Actually Requires
Think about the dialogue you remember from films or scripts you've read. Almost none of it is a character directly stating what they need. It's a character trying to get what they need while avoiding saying what they actually feel, using vocabulary and rhythm specific to who they are, in a way that reveals something about them whether they intend it to or not.
That's not stylistic flourish — it's structural. And it requires the writer (or the AI) to know three things simultaneously: what the character is after on the surface, what they actually want underneath that, and what they're protecting themselves from revealing. That's the psychological architecture. Without it, even technically accomplished dialogue reads like a transcript of a scene rather than a scene itself.
The problem with AI dialogue isn't the writing. It's that the AI is asked to write before it knows who anyone is.
This is why prompting harder doesn't fix it. Asking for "more naturalistic dialogue" or "sharper conflict" or "stronger character voices" gives the AI stylistic instructions without giving it the psychological foundation those styles need to emerge from. You get more confidently delivered generic dialogue, not genuinely different character voices.
The Difference Between Archetype and Character
Archetypes are categories. The grieving parent. The ambitious young executive. The burned-out detective. AI trained on scripts has seen thousands of examples of each archetype and will produce a competent version on request — because it's averaging the most common choices made by other writers in similar scenes.
Characters are specific. The grieving parent who makes inappropriate jokes when cornered. The ambitious executive who becomes weirdly still when she's angry rather than louder. The burned-out detective who is inexplicably kind to people he thinks are lying to him. Those specificities don't come from statistical averaging. They come from a writer deciding exactly who this person is and what makes them unusual within their situation.
| Archetype-level dialogue | Character-level dialogue |
|---|---|
| "I know what you're doing and it needs to stop." | "You know what, just — leave the dishes. I'll do them." |
| "This isn't what I signed up for." | "I keep thinking about that summer we drove to the coast. You remember? You didn't talk the whole way there." |
| "We need to talk about what happened." | "I rescheduled the dentist again. Third time. I just — anyway." |
| "I'm not angry, I'm disappointed." | "No, it's fine. It's completely fine. Do you want coffee?" |
The right column isn't better writing in isolation. It's better writing because it comes from someone who knows this specific person — their deflection habits, their avoidance patterns, the way they signal the exact opposite of how they feel. That knowledge has to exist before the first line is drafted.
What a Calibrated Approach Looks Like
The fix isn't more detailed prompting. It's structured psychological input before any dialogue generation begins. Character psychology mapping: surface objective, actual objective, emotional vulnerability. Relationship dynamic: the history, the power balance, the unspoken rules between these two people. And scene function: what's this scene doing for the story, and what does it cost each character to be in it.
When those three elements are established first, the dialogue that follows is shaped by them rather than by what an average script would do in a similar situation. The AI isn't averaging across its training data anymore — it's working from a specific psychological brief.
We can't keep pretending everything is fine between us.
ELENA
I don't know what you want me to say.
MARCUS
I want you to tell me the truth. That's all I've ever wanted.
ELENA
The truth? You can't handle the truth, Marcus. You never could.
MARCUS
Your brother called. Said to say hi.
Elena puts down her glass.
ELENA
When did you two start talking?
MARCUS
We don't. He just — he wanted me to know he knew. I think.
A long beat.
ELENA
I should have told you myself.
The second scene establishes conflict through what's being deliberately avoided. The brother is a stand-in for everything unspoken. Marcus's sentence that trails off tells you more about his state than a direct declaration would. And Elena's final line — which admits fault without explaining anything — lands with weight precisely because it doesn't over-explain. That restraint doesn't come from better prompting. It comes from the AI knowing, before it wrote line one, what Marcus can't bring himself to say directly and what Elena is genuinely afraid to confirm.
The One Change That Fixes Most AI Dialogue
Build the character before the scene. Not a biography — a psychological brief. What does this person want right now, what are they actually protecting, and what relationship history makes this specific conversation difficult. Five minutes of context produces dramatically different output than five minutes spent rephrasing the scene description.
The Dialogue & Character Film Prompt skill does exactly that kind of calibration before any line is generated — three targeted questions that extract the psychological architecture a scene needs to produce character-level rather than archetype-level dialogue.
Good dialogue isn't the writer telling you who a character is. It's a character revealing who they are through what they choose not to say. You can't get there by asking AI to write more naturally. You get there by giving it something specific to work from — which is what the character was always supposed to supply.
The next piece most people tackle from here is a podcast episode script with natural conversation flow. If you're working across the full Video & Pod workflow, the Video & Pod bundle covers everything in one place. For character work specifically, Claude vs ChatGPT for creative writing compares how each handles stylistic instruction and refusals. If Claude is refusing to write a specific scene entirely, here's the diagnostic for which refusal type you're hitting and the fix for each.
Common Questions About AI Dialogue
Put this to work: the Dialogue Character Film Prompt skill for Claude turns everything above into one guided workflow you run in a normal Claude chat. Not ready to buy? Start with a free Claude skill and see how it works first.