How to build a story bible with ChatGPT or Claude

6 min read · Updated October 23, 2026

An AI chatbot like ChatGPT or Claude is good at one part of keeping a story bible: reading your chapter and listing every name, description, date and event in it. That's the tedious part, and it's where a lot of authors give up. Used well, an AI turns a weekend of note-taking into an evening of checking.

The catch is that an AI is a fast, confident reader that sometimes misreads. Treat what it returns as a draft from an assistant, not as canon. The method below keeps the speed and catches the mistakes.

What AI does well for a story bible

• Extraction. Given one chapter, it can list characters, places, items, physical details, ages, titles and relationships, with quotes.
• Timelines. It can list the events in a chapter in story order and pull out any dates or time phrases.
• Comparison. Given your existing notes and a new chapter, it can point out where the chapter disagrees with the notes.
• Backfilling. Given a synopsis or series outline, it can build a rough starter bible for books you've already finished.
• Single-character sweeps. Given several chapters, it can collect every fact about one character.

What to watch for

Made-up facts

The biggest risk. An AI may fill gaps with plausible details your book never states: a hair color you didn't specify, a birth year worked out from a guess, a relationship it assumed.

Defenses:

• Ask for a quote for every fact, copied exactly from your text. If it can't quote it, it shouldn't record it.
• Ask it to mark each fact as stated outright or inferred. Review inferred facts with extra care.
• Spot-check quotes. Search your manuscript for a few of them. If one doesn't exist, check the rest of that reply closely.
• Tell it not to invent dates. Vague is better than wrong.

Truncation and skipped details

Chatbots have a limit on how long a reply can be. With a long chapter, the AI may stop partway, or quietly summarize the second half instead of extracting from it.

Defenses:

• One chapter at a time. Not the whole book.
• Ask it to say when it ran out of room, and to stop at a complete item rather than mid-sentence.
• Then ask it to continue from where it stopped.
• Compare against the chapter. If a character you know is in the chapter is missing, it skipped something.

Duplicates and name drift

Without your existing list of names, an AI will happily create "Kael," "Sir Kael" and "the Ember Knight" as three separate people. Give it the list of known names and aliases, and tell it to use the exact names.

Privacy

Your manuscript is unpublished work. Before pasting it anywhere:

• Check your AI account's data settings, including whether chats can be used for training and whether you can opt out.
• Consider what's in the chapter. Most fiction is low-risk; notes that include real people, private correspondence or contract details are not.
• Know where your bible lives. Copying a reply into a document or app means it's stored there too.

Prompt patterns that work

These patterns work in any chatbot. Adjust the wording to your book.

1. Extract one chapter

You are a careful continuity editor helping a novelist keep a story bible for The Ashen Crown. Read the chapter below and list every character, place, group and named object, with every fact the text states about each. For every fact, include the exact words from the text as a quote, and say whether it is stated outright or inferred. Use these exact names when the text refers to them, even by a nickname: Kael Varn (aka the Ember Knight, Sir Kael), Mara Thorne (aka the Grey Lady), Aldric Thorne (aka Lord Aldric)... Don't invent dates. If you run out of room, stop at a complete item and say so.

2. Build a timeline

List the events in the text below in story order, not the order they're told. For each, give the in-story date as precisely as the text allows, who was there, and where. The world uses its own calendar with months Frostmoon, Thawmoon, Seedmoon... Write dates like "3 Ashmoon 412". If the text only gives a relative time ("the next morning"), say so.

3. Continuity audit

Below are my story bible notes, followed by a new chapter. List every place the new chapter contradicts the notes or itself: descriptions, ages, dates, who is alive, who is where, who knows what, names, and the rules of magic. Quote the words from the chapter for each. Don't report things that are simply new.

4. Character sweep

Read the chapters below and list every fact about Kael Varn: appearance, history, abilities, possessions, relationships, and anything true of him at a particular time. Quote the text for each.

5. Brainstorm without breaking canon

Using the bible notes below, suggest three possible backstories for Brother Tolan that don't contradict anything established. Label every idea as a draft.

Ask for structure

Asking for a table or a fixed format, rather than prose, makes replies much easier to check and copy. Columns like entity, attribute, value, quote, stated or inferred work well.

A workflow for a whole manuscript

1. Set up the basics yourself. Main characters, their aliases, and your calendar, if you have one. This gives the AI names to match against.
2. Extract chapter by chapter, in order. Add new names to your known list as you go.
3. Review every reply. Keep stated facts that check out. Look hard at inferred ones. Delete anything without a real quote.
4. Build the timeline once the main facts are in. Then check ages, deaths and travel.
5. Run an audit on each new chapter as you write the next book.

Expect to spend real time on step 3. That's where the bible becomes trustworthy.

Connecting an AI directly to your bible

Copying and pasting works with any chatbot. Some tools also let an AI read and update your notes directly, so you can ask questions like "what color are Kael's eyes, and where did I say so?" in a chat.

Keep the author in charge

An AI can read faster than you, but it doesn't know which details matter, which contradictions are intentional, or which of two versions you prefer. Those decisions are the actual work of a story bible. Let the AI do the listing. Keep the judging for yourself.

For building a bible from a book that's already written, see a story bible for a finished book.