How to Build a Story Bible in Claude AI | Full Tutorial

Summary: How to Build a Story Bible in Claude (Claude AI) for Fiction

Core problem the tutorial addresses

• Claude forgets context between separate conversations, so writers who draft scenes without setup can get:
  • generic character results
  • continuity loss (e.g., character details, magic system costs, long-running tensions)
• The tutorial frames this not as a Claude “bug,” but as an LLM memory limitation.
• The solution is to externalize story context into a persistent reference document Claude can always access.

Key concept: the Story Bible as “institutional memory”

A story bible is the main reference document for a fiction project.

• It acts like a writer’s-room “source of truth” shared across contributors—except here Claude is treated as the second contributor.
• Unlike an outline (which tells what happens), the story bible describes the world and constraints that shape decisions.
• Using the iceberg principle, the story bible holds the “7/8 below the waterline”: rules, psychology, voice mechanics, backstory, and internal logic.

---

The recommended five-section Story Bible (works for most genres)

1. World brief (about 1 page)

Include:

• setting/period
• tone and emotional register
• world-specific rules
• genre-critical specifics, such as:
  • magic system history, costs, and limits
  • or (for contemporary fiction) subculture/professional codes

2. Character roster

• One entry per significant character, including:
  • name + physical description
  • role in the story
  • core want
  • core fear
  • the thing they’re most ashamed of
  • what they notice about a room others miss
  • the key hidden fact: “what nobody else in the story yet knows”
• Emphasis: the want/fear/shame triad is the most important material for:
  • consistent behavior
  • preventing “plot-convenience” acting

3. Voice guide

Focus on how Claude should generate prose in your narrative voice, not just a vague “style.”

Include technical settings such as:

• tense (e.g., first-person present vs third-person past)
• narrative distance (close vs omniscient)
• POV structure
• how interior thoughts are presented
• dialogue punctuation and pacing

Requires annotated examples from your own drafts, with explanations of what to replicate.

4. Timeline

Use two parts:

• events before page one (“pre-story” / pretory/backstory that governs the present)
• a running log as the manuscript progresses

Purpose:

• prevent continuity errors that are hard to notice mid-draft

Format is less important than consistency and clarity.

5. Rules and limits

Create a “promise register” of:

• what is allowed vs impossible in the story world

Include:

• internal logic
• technology presence/absence
• social power dynamics
• what characters know vs don’t know

Benefits:

• lets Claude push back or flag contradictions
• grows as new facts are added during drafting

---

Setup workflow inside Claude projects (so it persists across chats)

Steps

1. Create a new Claude project for the manuscript.
2. Add each story bible section as a separate document:
   • World brief
   • Character roster
   • Voice guide
   • Timeline
   • Rules and limits
3. Test it:
   • open a new conversation within the project
   • ask Claude to write a scene for the protagonist
   • check whether Claude gets:
     • character identity
     • voice
     • world rules
   • if it fails, the story bible likely has missing gaps

---

How to build each section (tutorial prompts and guidance)

World brief prompt

• Claude asks one question at a time
• You answer conversationally (as if explaining to a friend)
• Claude compiles the structured document at the end
• You’re instructed to push back if Claude requests irrelevant historical detail

Character entry prompt

Claude asks questions one at a time to capture:

• wants/fears/shame
• speech + movement mannerisms
• what they notice that others miss
• secret/unknown truth

Requirements:

• include dialogue examples (not vague descriptions), so Claude maintains consistent character voice

Clarification when Claude is wrong:

• apply the correction to both:
  • the scene correction
  • the character roster entry (to refine the bible)

Voice guide building approach

• Provide 3–4 passages you like from your drafts
• For each passage, annotate:
  • what specific technique to replicate
  • not just “good writing”

This helps prevent:

• generic prose
• internal drift in tense/POV

Timeline, rules/limits updates

• Add timeline entries as major events occur
• Expand rules/limits whenever new world logic must be preserved

---

The “consistency test” (Claude as a continuity editor)

Regularly run an audit prompt inside the project:

• Claude reads the story bible carefully
• you paste new draft text
• Claude flags contradictions/inconsistencies only (not style improvements)

Purpose:

• use Claude as a continuity checker, not just a scene generator
• forces the same workflow rhythm:
  • update the story bible
  • review the manuscript

Frequency guidance

• about every 20,000 words for a novel
• more frequently for shorter fiction

---

How to draft scenes with better prompts

Scene prompts should include specific constraints and context, not just “write a confrontation.”

A strong prompt structure includes:

• what the confrontation is about (e.g., the lie from chapter 3)
• POV choice (e.g., close third on a specific character)
• setting details (e.g., in the kitchen of Bee’s house; on Bee’s territory)
• emotional/tactical constraints (who has leverage; who’s disadvantaged)
• instruction to write “in my voice as defined in the voice guide”

With a story bible in the project, Claude doesn’t need the entire story context embedded in every prompt.

---

Keeping the story bible “alive” (most important maintenance rule)

Any new facts introduced during drafting must be added to the story bible before ending the session.

If you don’t update it for weeks/months:

• Claude will use stale context
• continuity errors will appear

Add/update for:

• newly discovered character details (phrases, laughter habits, relationships)
• world facts introduced in scenes (street names, years, prices)
• timeline entries for significant events
• new rules/limits established by events

---

Extensions for series fiction (beyond a single-book bible)

Keep the five core sections, but add two higher-level documents:

1. Series arc document

   • the largest-scale promises and central questions across multiple volumes
   • governs what each individual book must fulfill

2. Continuity log

   • cross-book facts that must remain consistent:
     • character ages and relationships to the timeline
     • world details established in book one
     • early foreshadowing that must be paid off later

Framing:

• for series, the story bible becomes “institutional memory” to prevent long-term continuity drift

---

Common failure patterns to avoid

1. Building a complete bible before writing any scenes
   • the story evolves; let the bible grow as writing reveals new truths
2. Making character entries too vague
   • generic traits lead to generic output; be specific enough to be unique
3. Updating the manuscript without updating the bible
   • creates contradictions when Claude continues drafting
4. Using Claude only for prose generation, not for audits
   • the consistency test is a separate workflow requiring an audit/flag mindset

---

Main speakers / sources

• “Claude for Fiction Writing” team / narrator (the channel/brand hosting the tutorial; no specific individual name given in the subtitles)
• Mentioned author: Ernest Hemingway (as the source for the iceberg principle)