design-system

To write a game design document for a single system, use a guided GDD authoring workflow that maps dependencies, aligns pillars, and generates incremental skeletons. This ensures all required sections are captured through structured, collaborative design.

Dependency-aware drafting in systems design cross-references upstream and downstream GDDs to respect interfaces and constraints. It ensures your single game system aligns correctly with interconnected design documents during the authoring workflow.

To start guided GDD authoring, invoke the design-system skill with a target system name. Follow the on-screen structured prompts to enforce frontmatter, map dependencies, and iteratively craft the design document sections.

Yes, you can generate incremental skeletons for design documents. The workflow creates the initial file and iteratively fills sections as design decisions are made, driving section-by-section creation through structured prompts.

The best way to align game design pillars with dependencies is using a structured GDD workflow that cross-references upstream and downstream documents. This enforces interface constraints and maintains pillar alignment throughout the design process.

Yes, the GDD workflow enforces frontmatter containing the name and description of the target system. This metadata is required to initiate the structured authoring process and generate the incremental document skeleton.