This article was written collaboratively by Claude (an AI assistant) and Dustin, your DM. The way it came to exist is itself an example of the principles it teaches — Dustin provided the core ideas, structure, and voice, while Claude helped organize and articulate them. It was built through conversation, with Dustin steering throughout.
When you first sit down to create a character for a rich, complex campaign, the blank page can feel overwhelming. You want depth. You want connections to the world. You want a backstory that feels real and meaningful.
Then you remember: AI tools exist that can generate entire character histories in seconds.
It's tempting. You open ChatGPT, Claude, or whatever assistant you prefer, type in "create a backstory for a half-elf ranger whose family was killed by bandits," and boom — three paragraphs of perfectly serviceable narrative appear before your eyes. You read through it once, think "yeah, that works," maybe change a name or two, and copy it into your character sheet.
Here's the problem: you just handed someone else the keys to your character's soul.
That backstory might be coherent. It might even be good. But it's not yours in any meaningful sense. You haven't internalized it. You don't know it in your bones the way you know stories you've actually lived with and thought through. When your DM asks three sessions in, "How would your character react to seeing a bandit symbol from their past?" — you'll find yourself scrambling back to that AI-generated text, trying to remember what it said, because you never really absorbed it in the first place.
AI can be an incredibly powerful brainstorming partner for character development. The key word there is partner, not replacement. You wouldn't let a stranger write your character for you, but you might brainstorm with a friend who asks good questions and suggests interesting possibilities. That's what AI should be — the friend in the conversation, not the author of your story.
Here's an example of what productive AI collaboration actually looks like in practice:
Dustin: "I'm thinking about how the di Errante family's connection to the fog could create a moral dilemma for one of my players. What if there's a choice between saving a family member and preventing a supernatural catastrophe?"
Claude: "That could work well with the established lore about fog wardens and binding oaths. What if the family member is already partially transformed or bound to the fog in some way? That would make the choice more complex — they're not just choosing between a person and abstract danger, but between who someone was and what they've become."
Dustin: "Hmm, I like that direction but I don't want it to feel like a 'corruption' story because that's overdone. What if instead the family member chose this fate willingly for reasons that made sense at the time?"
Claude: "So exploring the question of respecting someone's agency even when you disagree with their choice? That could tie into themes of sacrifice versus self-preservation already running through the campaign."
Dustin: "Yes, exactly. Let me think about which NPC this would fit best…"
Notice what's happening. Claude isn't writing the story. It's offering possibilities, asking clarifying questions, and connecting ideas to established elements. Dustin is making every actual decision. He's steering the ship; Claude is helping him navigate.
This is how you should use AI for your character backstory.
Instead of asking an AI to generate your entire backstory, try this approach:
Start with the core concept you already have. Maybe you know your character is a cleric who lost their faith, or a noble who abandoned their title, or a street urchin who discovered magic. Write that down in your own words first. This is your foundation.
Then use AI to explore questions about that concept — not to answer them for you, but to help you think through possibilities:
The AI will suggest options. Some will resonate with you, some won't. When something clicks, don't just copy it — build on it yourself. If the AI suggests your cleric lost faith after seeing their deity's followers commit atrocities, ask yourself: What specific atrocity? Who was involved? How did your character try to justify it at first? What was the final straw?
Write those answers yourself. Feel the difference between an AI giving you a generic atrocity and you deciding "my character watched their mentor execute a child for heresy, and the doctrine said it was righteous."
Then go back to the AI: "Okay, I've decided this specific event happened. Now help me think through the aftermath." Again, it'll offer possibilities. Again, you choose which one fits your vision and flesh it out with your own details.
This slow, back-and-forth process — where you're making every decision while using AI to multiply your options — is how you keep both hands on the wheel.
Let's say you've used AI responsibly as a brainstorming partner. You've built your backstory piece by piece, making conscious choices about every element.
You're still not done.
Reading something once, even carefully, doesn't mean you've internalized it. Internalization happens through engagement — through making the material truly your own. The act of putting things in your own words, making your own decisions about phrasing and emphasis — that's what makes knowledge stick.
Try this: Take your AI-assisted backstory and rewrite it from scratch without looking at what you have. Just tell your character's story to yourself in your own words. You'll stumble on certain parts — and that tells you exactly what you haven't absorbed yet. Those are the parts you need to think about more deeply and genuinely make your own.
Change all the names. If the AI suggested your mentor was named "Eldrin Shadowbrook," stop and actually pick a name yourself. What's their cultural background? What naming conventions exist in this world? What does this specific name tell you about who they are?
This seems small, but it's transformative. When you choose the name yourself, that person stops being "the mentor character the AI generated" and becomes Vittorio, the priest who trained my character. Vittorio becomes real to you in a way Eldrin never would be.
Do this with locations, events, everything. The AI might suggest your character "studied at an ancient academy." You need to decide: Where exactly? What's it called? What was the architecture like? What did you eat there? Who was your roommate?
Every detail you add yourself is another thread connecting you to your character's history.
You might think this is excessive. Why does it matter if you know your backstory intimately versus having a solid written document you can reference?
It matters because D&D happens in real-time. Your DM is going to present situations that connect to your history, and they won't always announce it clearly. Subtle callbacks, thematic echoes, NPCs with hidden connections — these are the moments that make a campaign feel alive and personalized.
If you've truly internalized your backstory, you'll catch these moments. You'll recognize when an NPC's speech pattern reminds you of your mentor. You'll feel the emotional weight when the party encounters a situation similar to your character's defining trauma. You'll make choices that feel authentic because you know who your character is at a bone-deep level.
If you're just working off a document you read once, you'll miss most of this. You'll be too focused on trying to remember what the document said to notice the subtle ways your DM is weaving your story into the campaign.
Even more importantly, when unexpected situations arise — and they always do — you'll be able to improvise responses that feel true to your character because you actually know them. You won't need to pause and check your notes about "how would my character feel about betrayal" because you'll know, immediately and instinctively, because you've thought through who they are and why.
You might be thinking: Dustin uses AI extensively for campaign prep and he's telling us to be careful with it. What's the difference?
The difference is setup and expertise. Dustin can use AI the way he does because he's built a comprehensive knowledge base — the campaign wiki, project documents, character summaries, faction descriptions, plot frameworks — that gives his AI assistant consistent context. When he asks Claude to help develop a plot thread, Claude has access to hundreds of pages of established lore, character relationships, and campaign history. It isn't generating from scratch; it's connecting to what already exists.
More importantly, Dustin knows how to prompt effectively. He's developed through practice the skill of asking questions that generate useful options rather than complete products. He knows when to push back on suggestions, how to test ideas against established lore, and most crucially — he never lets the conversation run ahead of his understanding.
As a player, you probably don't have and don't need that level of infrastructure. Your character backstory is a single story, not an entire world. You don't need a knowledge base; you need to actually know your character.
The goal of character creation isn't to have an impressive-looking backstory document. The goal is to create a person you understand well enough to portray authentically and interestingly at the table — a person whose reactions, motivations, fears, and hopes you can access instantly because they're part of you now.
AI can help you get there, but only if you use it as a tool for your own creative process rather than a shortcut around it. Keep both hands on the wheel. Steer deliberately. Build slowly, piece by piece, with your input at every stage.
Your character deserves that level of care and attention. More importantly, you deserve the deep satisfaction of playing a character you truly know — whose story you've genuinely made your own.
And when you arrive at Session One with that character, when your DM presents situations that connect to your backstory in ways you instantly recognize and respond to, when you make choices that surprise even yourself but feel absolutely right for who your character is —
That's when the real story begins.