design-system

Guide section-by-section GDD authoring with dependency cross-referencing and incremental file writes.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/CarlosQ96/robot-crawler --skill design-system-carlosq96
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-system
Source: https://github.com/CarlosQ96/robot-crawler/tree/main/.agents/skills/design-system
Command: npx skills add https://github.com/CarlosQ96/robot-crawler --skill design-system-carlosq96

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill provides a guided, collaborative workflow to author and maintain a single game's system design (GDD) by assembling context from existing docs, cross-referencing dependencies, and incrementally writing sections to disk.

Core Features & Use Cases

  • Guided, section-by-section GDD authoring across a single game system. The skill reads existing design docs to produce a complete system design skeleton and iteratively fills in sections as context evolves.
  • Cross-reference to dependencies and registry data to avoid conflicts and surface consistency issues.
  • Automatic, incremental writes to design/gdd files to support off-line collaboration and versioning.

Quick Start

Invoke /design-system <system-name> to create a skeleton at design/gdd/[system-name].md and start the guided, section-by-section GDD design workflow.

Frequently Asked Questions about design-system

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start writing a game design document collaboratively?

To start collaborative GDD authoring, invoke the command with a system name to generate a skeleton file on disk, then follow the guided section-by-section workflow to incrementally fill in the design.

What is the best way to maintain consistency across multiple game system design docs?

Maintain GDD consistency by cross-referencing dependency data and existing docs during authoring, which surfaces conflicts and enforces a standard format across all game system designs.

Can I use this guided authoring workflow for offline version control of game design docs?

Yes, guided authoring supports offline version control by automatically writing incremental design updates directly to disk, ensuring changes are saved for collaboration.

How does the GDD authoring process handle specialized architecture and balance decisions?

The GDD authoring process defers specialized architecture and balance decisions to dedicated roles, focusing its logic on aggregating context and guiding standard system sections.

Do I need existing design docs to generate a game system design skeleton?

No, you do not need existing docs to generate a game system design skeleton, though the workflow aggregates available context to iteratively refine sections as your design evolves.