design-system

To create a game design document, this skill guides you through a structured, section-by-section authoring process. It generates a skeleton and incrementally writes the content to a markdown file while collaborating with you to refine each section.

Writing a GDD incrementally is handled by appending to an existing design file while preserving prior work. The process cross-references dependencies and loads constraints to ensure traceability and consistency across systems without overwriting content.

Cross-system consistency in game design documentation is maintained by loading constraints from a systems index and registry. The authoring process cross-references these dependencies to ensure new content aligns with existing rules and traceability requirements.

Yes, you can use existing documentation as context when authoring a game system GDD. The skill gathers context from existing docs to inform the incremental drafting process and cross-reference dependencies for the new system design.

You need a systems index and registry to ensure consistency and traceability during guided GDD authoring. The skill loads constraints from these sources to cross-reference dependencies while incrementally writing the design file.

A limitation of using a collaborative agent for game system design is that it focuses on a single system at a time. It requires structured frontmatter for discovery and relies on existing system indexes to correctly cross-reference dependencies.