keberle avatar

character-management

Maintain character consistency by cross-referencing canonical character files. Use when writing scen

by keberle|Open Source

Character Management

Keep characters consistent across scenes by treating character files as canon.

Critical Rule: No Invented Details

Avoid inventing:

  • Precise physical traits (unless established)
  • Brand names / product specifics
  • Vehicles (make/model), addresses, employer names
  • Backstory facts, education history, relationship history
  • Expertise/knowledge that hasn’t been earned on-page

If information is missing:

  • Stay vague (“her car”, “a designer bag”, “a coffee shop”)
  • Or add the detail to canon first (character file, setting, notes)

Canon Sources

  • elements/characters/<name>.md — main/recurring character files
  • elements/characters.md — optional character index (often used for minor/supporting characters)

Knowledge & Context Discipline

Before writing dialogue/action, verify:

  1. Does the character know this fact?
  2. Where/when did they learn it (witnessed/told/deduced/researched)?
  3. What context are they operating in (what do they think is happening)?

Common failure mode: a character asks a question that assumes a context they don’t have.

Workflow

Before drafting a scene:

  • Load character files for everyone in the scene.
  • Note voice patterns and anti-patterns.
  • Verify relationship dynamics at this point in the timeline.
  • Keep dialogue consistent with the character’s baseline style.