Creative Lore-Keeper
Creative Lore-Keeper
The Problem
Chapter 1: your protagonist hates heights.
Chapter 7: she climbs a radio tower without hesitation.
Nobody caught it. The AI didn't. You didn't until a beta reader pointed it out.
This is the most common failure mode in long-form AI-assisted creative work. The AI processes each turn in isolation. It doesn't automatically re-check what it established ten scenes ago. Rules get forgotten. Characters drift. Timelines contradict themselves. Planted foreshadowing disappears.
The longer the project, the worse it gets.
How It Works
Before generating any creative output, this skill runs a five-axis consistency check against your established lore.
Every turn. Without being asked.
The Five Axes
Axis 1 — Character (CHR)
Checks that the character's voice, traits, history, and relationships match what was established. Catches: personality drift, forgotten backstory, contradicted abilities, relationship reversals.
Without this axis: A character who swore never to use magic casts a spell in scene 12. No one flagged it.
Axis 2 — World (WLD)
Checks that the setting, rules, geography, organizations, and in-world logic are consistent. Catches: locations that moved, rules that changed without explanation, organizations that contradict their own structure.
Without this axis: The city's northern gate — established as destroyed in chapter 3 — is used as an escape route in chapter 9.
Axis 3 — Timeline (TML)
Checks that events are in causal order and that the current scene's timing is consistent with established history. Catches: events that happen before their causes, ages that don't add up, seasons that shift unexpectedly.
Without this axis: A character references an event from "last winter" that the timeline shows happened three years ago.
Axis 4 — Dormant Lore (LORE)
Scans your established lore for elements that exist but haven't been used — and surfaces them as potential additions to the current scene. Catches missed opportunities: planted foreshadowing that was never paid off, named characters who disappeared, objects with unexplained significance.
Without this axis: The mysterious letter from chapter 2 is never mentioned again. The reader remembers it. The AI forgot.
Axis 5 — New Contradictions (CONT)
Compares the current output against the previous turn to catch contradictions introduced in this exchange. Catches: facts that shifted between turns, positions that reversed without cause, names that changed.
Without this axis: The antagonist's motive in this scene directly contradicts what was established two turns ago.
Entity Extraction
Before running the five-axis check, the skill scans your message for:
- Named entities (characters, places, organizations, objects)
- Roles and titles ("the king", "her mentor", "the guild master")
- Events referenced ("the battle", "when she left", "before the war")
- Any point where the AI would normally say "I think" or "probably" — these are the spots most likely to contain a hidden contradiction
The extracted entities are what drive the consistency check. If a character is mentioned, all five axes check against that character's established lore.
Active Lore Suggestions
After the consistency check, the skill surfaces 1–3 unused story elements that could enrich the current scene.
These are not generic suggestions. They come from your established lore:
- A named character who hasn't appeared recently and whose presence would be meaningful here
- A planted detail from earlier in the story that could pay off in this scene
- A world-rule or setting element that would add texture without introducing contradiction
Every suggestion includes the lore reference it comes from, so you can verify it yourself.
Before / After
Before:
Scene 14: Marcus drew his sword — the one his father had given him before the execution.
After (with Creative Lore-Keeper):
[Axis 1 — CHR]: Lore established in Scene 3: Marcus's father died when Marcus was an infant. He never knew him. A sword "given by his father" contradicts this.
[Axis 4 — LORE]: Unused element available: the mentor's blade, described in Scene 6 as "the only thing Marcus kept from his training."
Suggestion: Replace "father's sword" with the mentor's blade — this pays off the Scene 6 detail and stays within established lore.
Hard Rules
- Five-axis check runs every turn. It is not optional, not skippable for "quick" scenes, and not replaced by the AI's general confidence that things are consistent.
- Entity extraction precedes the check. The check only works if named entities, titles, and events are first extracted from the current message. Skipping extraction and running the check from memory defeats the purpose.
- Axis 4 must surface at least one unused element per turn, or explicitly state none exist. "None found" is acceptable. Skipping the axis is not.
- Active lore suggestions must cite their source. A suggestion without a lore reference is an invention, not a suggestion. All suggestions trace back to established content.
- Contradictions are reported before generating output. If a contradiction is found, it is flagged and the human decides how to proceed — the AI does not silently choose the interpretation that makes the current scene work.
- "I think it was established that..." is a trigger to check, not a basis for output. Any moment of uncertainty about established lore requires a check, not a guess.
