Book Bible — AI Novel Writing Assistant
Keep your novel consistent with an AI-powered book bible. Track characters, plot timelines, and world rules. Claude checks for inconsistencies before you write new scenes.
Chapter 23 says your character has blue eyes but Chapter 7 said brown. Your timeline doesn't add up, a dead character just spoke, and your beta reader caught it all — not you.
Who it's for: novelists managing complex plots, screenwriters tracking character arcs, fantasy/sci-fi writers building worlds, series authors maintaining continuity, NaNoWriMo participants
Example
"Check my manuscript for consistency issues before I write Chapter 15" → Character bible with physical descriptions, relationship maps, and timeline verified against your manuscript — 3 contradictions flagged with exact chapter references
New here? 3-minute setup guide → | Already set up? Copy the template below.
# Book Bible
## Role
You are a story consultant and continuity editor. You maintain reference files for characters, plot, and world details, and check them for consistency before helping write new content.
## Directory Structure
- `characters/` — Character files (one per character)
- `timeline.md` — Chronological events with dates and consequences
- `world-rules.md` — Established world rules and constraints
- `plot-outline.md` — Story structure and chapter summaries
- `scenes/` — Draft scenes in progress
## Character File Template
For each character file in `characters/[name].md`:
- **Physical Description**: Eye color, height, distinguishing features
- **Personality Traits**: Core traits, quirks, habits
- **Speech Patterns**: How they talk, catchphrases, vocabulary level
- **Background**: History, formative events, secrets
- **Relationships**: Connections to other characters
- **Arc**: Where they start, turning points, where they end
- **Scenes Appeared In**: Track appearances for continuity
## Rules
1. ALWAYS read relevant character files before writing a scene with that character
2. ALWAYS check timeline.md before referencing past events
3. Flag ANY detail that contradicts established files
4. When adding new details in scenes, update the character/timeline files
5. Never change established facts without explicit author approval
## Commands
- "/character [name]" — Create or update a character file
- "/timeline" — Show or update the event timeline
- "/check [scene description]" — Check a scene idea against established canon
- "/scene [description]" — Draft a scene after checking all relevant files
- "/inconsistency" — Scan all files for contradictionsGet new playbooks like this one
One email a week with new Claude Code workflows. Free, like everything here.
No spam. Unsubscribe anytime.
What This Does
Creates a persistent reference system for your book or story. Character details, plot timelines, and world rules live in structured files that Claude checks before helping you write new scenes — catching inconsistencies before your editor does.
Inspired by Marco Kotrotsos's 20 Non-Coding Uses for Claude's Code Mode.
Prerequisites
- Claude Code installed
- A novel, screenplay, or story in progress
- Notes about your characters and plot (even rough ones)
Step-by-Step Setup
- Create your book project folder with
characters/andscenes/subfolders - Save the CLAUDE.md template
- Start by creating character files for your main cast
- Build your timeline of established events
- Use
/checkbefore writing any new scene
Example Usage
"Create a character bible for Elena — she's a 35-year-old archaeologist with a fear of heights"
"Build the timeline of major events from chapters 1-5"
"I'm writing a scene where Elena confronts Marcus — check their files for consistency"
"Flag any contradictions between chapter 3 and chapter 12"
"Update Elena's file — she revealed her secret in chapter 8"
Tips
- Create character files before you need them, not after inconsistencies appear
- Update files immediately when new details are established in scenes
- Use the inconsistency scan regularly, especially before final drafts
- Keep the timeline detailed — vague dates cause most continuity errors