What problem does it solve?
Game design documents (GDDs) often contain conflicting values for the same entities, items, formulas, or constants across different files, leading to broken game mechanics, wasted development time, and costly rework when these inconsistencies are caught late in the development cycle.
Core Features & Use Cases
- Cross-Document Conflict Detection: Scans all GDDs against the central entity registry to flag mismatched stats, values, and formula variables.
- Targeted or Full Audits: Supports checking a single specific entity/item or running a full audit of all registered entries across all GDDs.
- Traceable Conflict Logging: Automatically logs all detected conflicts to a dedicated failure log for team visibility and historical tracking.
Use case: A game designer can run this skill immediately after finishing a new combat system GDD to ensure all entity stats match the values defined in the core registry before moving on to architecture work.
Quick Start
Run the consistency-check skill after completing any new game design document to scan for cross-document value conflicts and get a clear report of any issues to resolve.