Claude for Fiction: Scenes, Characters, Continuity, and Voice

Build a story bible before drafting

Fiction work with Claude improves when the model can see the rules of the invented world. A story bible gives it a stable reference for characters, timeline, setting, point of view, taboo words, and unresolved questions.

Keep the story bible factual and current. Do not ask Claude to remember canon that is scattered across ten old chats. Put the living canon in a project document and update it after major decisions.

The aim is not to make Claude the author. The aim is to prevent the assistant from breaking the story you are authoring.

• Character sheets: desire, fear, secret, contradiction, voice markers.
• Timeline: what the reader knows, what the character knows, what is still hidden.
• Scene rules: point of view, tense, distance, and forbidden exposition moves.
• Continuity ledger: injuries, objects, promises, deadlines, and unresolved clues.

Ask for scene pressure, not decorative prose

Generic AI fiction often fails because it decorates instead of dramatizing. A better prompt asks Claude to inspect the scene engine: whose desire drives the moment, what changes by the end, what information is withheld, and what line of action creates pressure.

Once the mechanics are clear, ask for three possible beats rather than a polished scene. Pick or alter the beats yourself. Then draft the scene, or ask Claude for a rough pass that you treat as scaffolding rather than finished prose.

If Claude writes too smoothly, interrupt it. Ask for less explanation, sharper conflict, more subtext, or a version where the character refuses to say the obvious thing.

Protect voice with examples and exclusions

Voice is not a mood label. "Lyrical," "gritty," and "funny" are too vague. Give Claude short excerpts of your own work and annotate what matters: sentence length, compression, image logic, humor, restraint, profanity, rhythm, and what you never do.

Then add exclusions. Claude is prone to smoothing rough edges because helpfulness often sounds like tidiness. Tell it which asymmetries are intentional: fragments, silence, vernacular, abrupt transitions, recurring obsessions, or withheld explanation.

If you use custom styles or skills, keep them specific to repeatable workflows. A "voice skill" should include examples, do/do-not pairs, and tests Claude must apply before revision.

• Use two excerpts you like and one excerpt that shows a common mistake.
• Ask Claude to name the voice rules before it rewrites.
• Keep final line edits human, especially for rhythm and surprise.

Use Claude as a continuity clerk

Claude can be very useful after you draft. Paste a chapter or scene and ask it to produce a continuity ledger: timeline, physical state, promises made, emotional state, open questions, and contradictions with known canon.

This is less glamorous than generating prose, but more valuable over a long project. Continuity errors accumulate quietly. A structured ledger turns them into fixable work.

For multi-chapter analysis, put long documents first, then the question and task at the end. That ordering follows Anthropic long-context guidance and reduces ambiguity in complex document prompts.

1. Paste the canon summary and chapter text.
2. Ask for a table of claims, open loops, and possible contradictions.
3. Accept only concrete references, not vague vibes.
4. Update the story bible after human review.