design-system

A guided game design document (GDD) system authors a complete single-system GDD section-by-section, walking you through core rules, formulas, and acceptance criteria to ensure no required sections are missed.

Retrofit mode for game design documents detects which sections are missing or contain only placeholders, filling in those specific gaps without overwriting your existing completed content.

To maintain cross-system consistency, the drafting process reads the game concept and systems index first, resolves dependencies, and surfaces upstream and downstream constraints before writing.

Yes, authoring a structured GDD requires reading prerequisite documents like the game concept and systems index to map dependencies and enforce consistency across the project.

Dependency mapping for systems design is handled by identifying upstream and downstream systems, extracting their key interfaces and assumptions, and warning you about undesigned dependencies before drafting.

Yes, game systems design supports incremental drafting by guiding you through structured sections including formula specification, tuning knobs, and edge cases, writing each to the correct file.