design-system

Automate guided GDD authoring with structured sections and dependency tracking.

Updated Apr 25, 2026

Search Tags:#workflow #documentation #design-system #game-design #design-doc #gdd

Ready to run

npx skills add https://github.com/packetalien/cursor-game-studios --skill design-system-packetalien

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design-system
Source: https://github.com/packetalien/cursor-game-studios/tree/main/.cursor/skills/design-system
Command: npx skills add https://github.com/packetalien/cursor-game-studios --skill design-system-packetalien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Design System Skill helps game teams craft a complete, consistent GDD for a single system, by guiding authors through required sections, cross-checking dependencies, and incrementally writing to the design doc.

Core Features & Use Cases

Auto-generates a structured skeleton and frontmatter for new systems, ensuring consistency with the studio's standards.
Walks through required GDD sections (Overview, Player Fantasy, Detailed Design, Formulas, etc.), surfacing dependency and feasibility constraints before drafting.
Supports incremental collaboration by staging sections, validating against dependency GDDs, and enabling on-demand updates.

Quick Start

Invoke the design-system skill with a target system name to begin scaffolding its GDD.

Frequently Asked Questions about design-system

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

FAQPage Schema

How do I write a game design document for a single system?▼

To write a game design document (GDD) for a single system, you need guided authoring that automates context gathering and scaffolds required sections like Overview, Player Fantasy, and Detailed Design. This process incrementally builds a structured design doc with enforced frontmatter and traceable dependencies.

What is guided GDD authoring and how does it work for game design?▼

Guided GDD authoring is a workflow that orchestrates context gathering and section scaffolding across discovery, feasibility, drafting, and validation phases. It coordinates with dependencies and cross-system constraints to deliver a structured design document with modular sections.

How do I scaffold a design doc with enforced frontmatter and modular sections?▼

To scaffold a design doc with enforced frontmatter, you auto-generate a structured skeleton and frontmatter for new systems. This ensures consistency with studio standards by walking through required GDD sections and surfacing dependency constraints before drafting.

Can I validate a system design doc against cross-system dependencies?▼

Yes, you can validate a system design doc against cross-system dependencies. The workflow supports incremental collaboration by staging sections and validating against dependency GDDs, surfacing feasibility constraints before and during drafting.

Does GDD authoring work for incremental collaboration and staging sections?▼

Yes, GDD authoring supports incremental collaboration by staging sections, validating against dependency GDDs, and enabling on-demand updates. This allows authors to write to the design doc incrementally while maintaining cross-system consistency.

What are the limitations of scaffolding a single game system design doc?▼

Scaffolding a single game system design doc is limited to one system at a time and requires coordinating with existing dependency GDDs. It focuses on discovery, feasibility, drafting, and validation phases rather than holistic project management.