What problem does it solve?
Game design teams often produce incomplete, inconsistent game design documents (GDDs) that miss critical sections, contradict existing system rules, or fail to align with established game pillars and engine constraints, leading to costly rework and implementation gaps during game development.
Core Features & Use Cases
- Structured Section-by-Section Authoring: Walks through 8 mandatory GDD sections (Overview, Player Fantasy, Detailed Design, Formulas, Edge Cases, Dependencies, Tuning Knobs, Acceptance Criteria) incrementally to ensure no required content is missed.
- Context-Aware Design: Automatically pulls existing game concept docs, system dependencies, entity registry data, and past consistency failure logs to avoid contradictions with already finalized design decisions.
- Retrofit Mode: Fills gaps in existing incomplete GDDs without overwriting completed content, making it easy to update legacy design documents without starting from scratch.
Use Case: A game designer building a new inventory system can use this skill to pull existing item registry data and economy system rules, walk through each required GDD section with guided prompts, and ensure the new design aligns with already finalized crafting and progression systems.
Quick Start
Use the design-system skill to author a complete, consistent GDD for your new player combat system, with all required sections filled via guided prompts and cross-referenced context from your existing game docs.
