My game is a single-player RPG set inside one walled city with 40 named NPCs. Every one of them needed at least one conversation tree, and the important ones needed three: a first meeting, a mid-game check-in, and a post-quest resolution. Do that math and you land somewhere around 100 trees. I am a solo developer. I am, very specifically, not a professional dialogue writer. I opened the empty dialogue files, looked at them for two full days, made a cup of tea, looked at them some more, made a worse cup of tea, and then finally admitted I needed a system instead of a vibe.
The thing that paralyzes you about NPC writing at scale isn't any single conversation. It's the sheer combinatorial dread of knowing that the blacksmith, the innkeeper, the suspicious guard, and 37 others all have to sound like distinct human beings, and that if they all start sounding like me-typing-quickly, the city dies. Sameness is the enemy. A city where everyone has the same voice is a city with one inhabitant wearing 40 hats.
The template that goes in before the prompt
Before I touch the AI, I fill a tiny five-field card for each NPC: name, role, a two-to-three-word personality, where in the story they appear, and one secret or fact they actually know. That card maps one-to-one onto the variables in the Branching NPC Dialogue Tree With Personality, Lore Gates, and Dead Ends prompt, which I run on Claude Opus 4.8. The XML-ish tags in the prompt matter more than I expected — keeping personality, quest context, and lore in clearly separated blocks meant Claude never blurred them into one beige character. I'd tried looser, paragraph-style prompts before and gotten exactly that mush.
What Claude is genuinely good at here
Voice consistency is the standout, and it's the hardest thing to do by hand across 40 people. My blacksmith is 'gruff but secretly kind.' Claude wrote every one of his lines with a surface bark that softens at exactly the right moment, and — this is the part I could never do reliably — it never narrates the softening. It just lets a hard man say one quiet thing and then change the subject. The rule in the prompt forcing a deliberate dead end produced some of my favorite writing in the whole game. The innkeeper who flatly refuses to talk about the cellar is more memorable than three NPCs who cheerfully explain the entire plot, because the refusal implies a story the player has to go dig for.
- 40 NPCs' first-meeting trees done in 12 days, working only evenings and weekends
- About 20 minutes of editing per generated tree, versus the 2 hours it took me to write one cold
- Playtester feedback forms specifically praised 'believable, distinct NPCs' more than once
- I finished the batch still wanting to write more, which has genuinely never happened to me before
The variable that does the most work
It's npc_personality, and it's not close. Two or three precise adjectives completely reshape what Claude hands back. 'Nervous and evasive' gives me clipped sentences, deflections, and little stage directions like 'he glances at the door before answering.' 'Jovially dishonest' gives me warmth wrapped around logic that doesn't quite hold up if you press it. 'Weary and philosophical' slows the whole rhythm down and adds metaphors about time. I now spend more time on those three words than on every other field combined, and it's the single highest-leverage edit I make to any tree.
The second-most-useful field is the one secret. Giving each NPC exactly one thing they know — and gating it behind a real choice via the lore-reveal tag — means even my minor characters feel like they have an inner life the player can choose to crack open or walk past. That optionality is what turns a quest-dispenser into a person.
My honest caveat: about one tree in six needs a real structural pass, almost always because Claude made every branch a little too cooperative and I had to harden a dead end or add a genuine cost to a choice. That's editing, not writing, and editing is the part I'm actually good at, so the trade is heavily in my favor. The model gets me to a strong draft; I get it to feel like mine.
If you're a dev drowning in empty dialogue files, grab the Branching NPC Dialogue Tree With Personality, Lore Gates, and Dead Ends prompt on Prompt Dock and feed it your weirdest, most specific character first — that's where it shines hardest. When I want the secret an NPC is guarding to feel like it belongs to a real history, I generate that history first with my Lore Bible Entry — Faction, Region, or Historical Event With Built-In Quest Hooks prompt and paste a single line of it into lore_to_reveal. The two together make a city that feels like it remembers things from before you arrived.