A story bible is not a museum for every idea you have ever had. It is the compact, reliable reference that tells you—and any AI collaborator—what is true in the story right now.
Without one, each new prompt becomes a fresh negotiation. Names shift, locations change character, and a decision made three scenes ago quietly disappears. With one, you can explore freely while protecting the continuity that makes a fictional world believable.
Start Small and Make It Useful
The best story bible is easy to consult while writing. Begin with five records:
- Premise: the central promise of the world and the conflict it makes possible.
- Rules: the limits of technology, magic, society, travel, power and information.
- People: each important character’s goal, fear, relationships and current state.
- Places: the few locations that shape the plot, including their sensory and social character.
- Timeline: the past events and current pressures that make the present story inevitable.
The goal is not exhaustive detail. It is to answer the questions that would otherwise make a scene inconsistent. A one-sentence rule such as “messages cannot cross the storm belt without a physical relay” can do more work than pages of decorative lore.
Separate Canon from Possibilities
AI is brilliant at producing options. That makes a clear status for each note essential:
| Status | Meaning | How AI should treat it |
|---|---|---|
| Canon | Approved and binding | Preserve it unless you explicitly ask to revise it. |
| Working | Likely, but not confirmed | Use it cautiously and flag assumptions. |
| Open | A question worth exploring | Generate alternatives instead of pretending it is settled. |
| Rejected | No longer part of the world | Do not revive it accidentally. |
This distinction keeps exploration playful. You can ask for five possible origins of a forgotten city without allowing the first appealing answer to become the official history.
Give AI a Focused Context Packet
Do not paste an entire archive into every prompt. For a new scene, select only the relevant world rules, character records and location details. Then give the model a precise job.
Here are the approved facts for Mara, the harbour district and the storm-belt rule. Propose three ways Mara could obtain a relay key without contradicting any canon. Label every new assumption.
The request is useful because it names the boundaries. It also creates a reviewable output: you can choose one path, update the relevant records, and leave the other paths as experiments.
Revise the Bible Through Decisions
Each completed scene should prompt a tiny update. Ask: what did this scene establish, change or make impossible? Add only those outcomes. This lets the world evolve at the same pace as the story.
For more on how the records feed narrative layers, continue with AI-Assisted World-Building . The story bible holds context; scenes put that context under pressure.
A Practical Record Format
Use a consistent record for every important entry. The format below is deliberately small enough to maintain while drafting:
| Field | Example question |
|---|---|
| Summary | What is this person, place or rule in one sentence? |
| Status | Is it canon, working material, open or rejected? |
| Connections | Which characters, locations, events and rules does it affect? |
| Evidence | Which scene, note or decision established it? |
| Consequence | What later choice or conflict does it make possible? |
Suppose the story bible says that a storm belt prevents normal communication. The useful entry is not just “messages cannot cross the belt.” It records that the harbour relay is controlled by Mara’s brother, that a failed crossing caused a past tragedy, and that the rule isolates the city during the current crisis. Now a scene involving a missing message carries both plot and emotional weight.
Maintain It in Short Sessions
Do not interrupt every burst of writing to update the bible. Instead, reserve a ten-minute review after a scene or planning session. Capture only decisions that survived the draft:
- Add any new approved fact.
- Change an entry that the scene has made obsolete.
- Link the fact to the scene where it mattered.
- Record any new open question for later exploration.
This rhythm prevents a common failure mode: maintaining a beautiful reference system that is disconnected from the actual story. The bible is valuable only when it reflects the work you are making now.
Common Mistakes to Avoid
- Writing an encyclopedia before writing scenes. Start with the rules and relationships that create immediate pressure, or develop a topic map that reveals what the next scenes actually need.
- Recording generated suggestions as fact. Keep AI proposals in a separate working area until you approve them.
- Duplicating information. A character’s occupation should have one authoritative record, linked from other entries rather than copied repeatedly.
- Forgetting consequences. A fact that never changes a choice may be flavour, not essential canon.
Quick Check Before You Continue
Before moving to the next sequence, can you answer these questions in under a minute?
- What is definitely true in this moment of the story?
- Which character is most affected by that truth?
- Which detail is still open to experimentation?
- Where will a future writer—or future you—find the decision behind it?