design-system

Guided section-by-section game design document authoring enforces consistency by collecting game context, mapping dependencies, and drafting incrementally with approval gates. It reads upstream system facts to prevent cross-system contradictions during GDD creation.

Retrofitting an incomplete game design document detects missing sections and fills placeholders using non-destructive edits. The workflow validates existing GDD content, normalizes system names, and preserves original text while appending only required new sections.

Dependency mapping identifies upstream and downstream systems by reading the systems index, then surfaces interface, formula, and edge-case assumptions that must be respected. This constraint-aware integration ensures the new system design fits the existing game architecture.

Authoring a system game design document requires a YAML-frontmatter-configured workflow, a game concept file, and a systems index for context reads. A feasibility pre-check validates these inputs and normalizes system names before skeleton creation begins.

The best way to structure a game design document is through a skeleton creation phase that lays out all required sections from Overview through Acceptance Criteria. Approval-gated drafting then fills each section incrementally, ensuring full system coverage.

Cross-system contradictions occur when game design documents are authored without reading the game concept, entity registry, and prior consistency failure patterns. Context-first design pulls these facts in before drafting to validate interfaces and enforce dependency-aware constraints.