Lore & IP Consistency Validator
Audit game lore for contradictions, timeline gaps, and canon conflicts
What You Can Do
You can upload your complete lore documentation—quest texts, character bibles, environmental storytelling, dialogue scripts, timeline documents—and Claude will cross-reference them to flag contradictions, retcons, timeline inconsistencies, and canon gaps. The skill creates an auditable lore database that tracks which content is authoritative, identifies what's been retconned, and highlights missing connective narrative tissue across your IP.
Features
Scans multiple narrative documents simultaneously and flags conflicting character backstories, timeline events, world rules, and plot points with specific source citations
Establishes authoritative canonical versions when contradictions exist, tracking which content is primary canon, secondary canon, or non-canon (retconned)
Verifies chronological consistency across all dated events, character ages, historical narratives, and story progression sequences
Traces character arcs, relationship changes, and personality consistency across quests, dialogue, and environmental storytelling to catch retcons or inconsistencies
Identifies missing lore connections, unexplained world mechanics, and narrative threads left unresolved that create immersion breaks
Builds an interconnected map of how characters, locations, factions, and plot points relate across your entire narrative ecosystem
Pre-validates new content against existing lore before implementation to prevent canon conflicts
Generates comprehensive lore validation reports highlighting risk areas, required fixes, and consistency scores for narrative review and sign-off
Example Output
Example 1: Character Contradiction
CONTRADICTION FLAGGED: Character Age Inconsistency
Character: Kael Thorne
Conflict: Quest_MainLine_Act2 states Kael is 32 years old (Year 247). Character_Bible_v3 establishes birthdate as Year 220, making him 27 in Year 247.
Source Documents: quest_line_act2.md (line 145) vs character_bibles/kael_thorne.md (line 23)
Severity: HIGH — Breaks character biography
Resolution: Update character age in Character_Bible_v3 to Year 215 birthdate OR revise quest dialogue.
Example 2: Timeline Gap
TIMELINE GAP IDENTIFIED: Unresolved Narrative Thread
Location: Ashenmoor Kingdom
Gap: Timeline_Master.md documents the Fall of Ashenmoor in Year 215. Environmental_Storytelling_Ashenmoor.md references "the rebuilding period" (Year 220+) but provides no narrative bridge explaining how the kingdom recovered or who led reconstruction.
Source Documents: timeline_master.md vs environmental_storytelling/ashenmoor.md
Severity: MEDIUM — Creates worldbuilding inconsistency
Recommendation: Add 2-3 lore entries bridging Year 215-220 recovery period.
What's Included
- SKILL.md: Complete instruction file with lore validation methodology
- Lore_Audit_Template.md: Structured template for documenting your game's canon hierarchy, character timelines, and worldbuilding rules
- Contradiction_Tracking_Sheet.md: Checklist for logging discovered inconsistencies with severity levels and resolution status
- Timeline_Verification_Framework.md: Step-by-step guide for cross-referencing chronological events and character ages across documents
- Stakeholder_Report_Template.md: Ready-to-use format for presenting lore audit findings to narrative leads and producers
Who It's For
- Narrative Designers — Validating quest text, dialogue, and story structure for internal consistency
- Lore Architects — Managing comprehensive worldbuilding documentation and IP canon databases
- Senior Writers — Reviewing work from multiple narrative team members before implementation
- IP Producers — Ensuring franchise consistency across games, DLC, and transmedia content
- QA Narrative Leads — Documenting lore bugs and continuity errors discovered during playtesting
Best For
- Consolidating multi-writer narratives — Identifying contradictions when lore comes from different authors
- Pre-DLC/expansion validation — Verifying new content doesn't conflict with existing canon
- Onboarding new writers — Establishing authoritative lore references and canon hierarchy
- Canon retcon resolution — Tracing contradiction origins and determining which version is authoritative
- Stakeholder narrative review — Generating audit reports that demonstrate lore quality and consistency
You might also like
You convert business process descriptions into structured data specifications that technical teams can implement without follow-up questions. The skill generates detailed data dictionaries specifying what data exists, how it flows, what quality standards it must meet, retention timelines, and compliance requirements. This bridges the communication gap between business stakeholders and data engineers, architects, and compliance officers.
by gadievron
You can design, validate, and optimize complex branching narratives by mapping narrative topology, analyzing player agency across choice points, tracking narrative promises (narrative debt), and maintaining consistency across diverging story branches. This skill helps you forecast development scope, identify narrative contradictions before they become costly, and ensure player choices feel meaningful rather than illusory.
by gadievron
You can systematically architect complex worlds where every system influences others, creating authentic cause-and-effect chains that drive narrative. This skill helps you map dependencies between geography and trade, politics and conflict, culture and faction dynamics, then identify logical inconsistencies before they break immersion. You'll produce consistency documents, lore frameworks, and faction relationship maps that support multi-author projects and branching storylines.
by gadievron
This skill transforms Claude into a lore auditor that catches contradictions across your entire narrative ecosystem—character ages, timeline placement, geography, personality consistency, and thematic integrity. You submit your lore documents, established canon, and new content together, and Claude flags logical inconsistencies, temporal conflicts, spatial incoherence, and potential player-facing plot holes before expensive production phases like voice acting or animation begin.
by gadievron
This skill runs a deterministic multi-stage pipeline to validate that each vulnerability finding from your scanner is real, reachable in production code, and genuinely exploitable. You eliminate wasted effort on false positives, unreachable code paths, and findings with impossible prerequisites—ensuring your exploit development team only works on findings that matter.
by gadievron
You can upload complex dialogue documents and have Claude analyze their branching structure for logical inconsistencies, tonal drift, pacing issues, and player agency problems. Claude validates that character voices remain consistent across multiple writers' contributions, maps decision architecture to ensure choices matter narratively, and identifies dead-end conversations or unresolved dialogue threads. The result is a structured audit with actionable recommendations for optimization before dialogue implementation into branching engines like Yarn, ink, or Dialogue Flow.
by gadievron
You can design multi-path narratives that feel coherent and meaningful by modeling how player choices create cascading consequences across story branches. This skill helps you track character state changes, dialogue dependencies, and narrative convergence points—ensuring that player agency feels genuine, not illusory. You'll identify and eliminate plot holes, false choices, and continuity errors before they reach players.
by gadievron