Lore Consistency Validator
Validate game lore for contradictions, timeline conflicts, and canon violations
What You Can Do
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.
Features
validates character ages, timeline placement, cause-and-effect sequences, and historical event dating across documents
identifies geography conflicts, inconsistent location relationships, and travel distance impossibilities
flags personality trait shifts, motivation contradictions, knowledge state errors, and relationship arc violations
distinguishes between core lore and retconnable content, preventing contradictions with established canon
assesses how story elements reinforce or undermine your narrative's core themes
compares lore bibles, design briefs, dialogue scripts, environmental storytelling, and legacy content simultaneously
prioritizes contradictions by impact level, highlighting issues before voice acting, animation, or localization
classifies errors as player-facing, internal inconsistencies, or minor continuity notes for triaging fixes
Example Output
Input: Lore bible excerpt (character is 25 years old in Year 1), dialogue script (character mentions "when I was a child 30 years ago"), and location map showing 2-day travel distance between locations connected by 8-hour dialogue reference.
Output:
- 🚨 CRITICAL CANON VIOLATION
Character Age Conflict (Player-Facing)
- Lore Bible: "Alex is 25 years old at game start (Year 1)"
- Dialogue Script (Act 2): "I was just a child 30 years ago when the war started"
- Issue: Character would be -5 years old at war start. Contradiction visible to players.
- Fix Options: Adjust character age to 55+ OR change dialogue to "10 years ago"
- ⚠️ SPATIAL INCONSISTENCY
Travel Time Conflict (Production Friction)
- Location Map: Forest to Capital = 2 days travel (distance marked 120km)
- Dialogue Reference (Act 1): "I rode to the Capital in 8 hours"
- Issue: Impossibility flagged. Affects player expectations if they traverse this path.
- Recommendation: Adjust travel time in dialogue or add story reason for faster route
✓ CONSISTENT
Character Motivation Arc: Alex's leadership values established in Act 1 dialogue align with Lore Bible background (trained by mentor figure) and reinforced through Act 3 decisions.
What's Included
- SKILL.md instruction file: systematic validation framework and lore-checking methodology
- Lore audit checklist template: canonical categories to validate across your documents
- Canon hierarchy worksheet: distinguish core vs. retconnable lore for your project
- Timeline conflict detector prompt: pre-built prompt for chronological consistency checks
- Character consistency matrix: track traits, knowledge, relationships across narrative documents
Who It's For
- Narrative Designers — validate new story content against established lore before implementation
- Game Writers — catch continuity errors in dialogue scripts and quest narratives early
- Creative Directors — maintain narrative coherence across multi-document IP and cross-media projects
- Lore Managers — systematically audit game bibles and legacy content during expansion or sequel planning
- QA Leads — identify plot holes and contradiction types to brief testing teams on what to verify
Best For
- DLC and expansion content integration into existing lore
- Pre-production lore review before voice acting, animation, or localization
- Onboarding new narrative writers to prevent contradictions in their first submissions
- Cross-media narrative validation (game → show → comic → novel alignment)
- Legacy content audit during narrative reboots or sequel planning
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 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.
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 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