design-system

Guide section-by-section GDD authoring with game, registry, and dependency context.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/easonlao/jiazi-game --skill design-system-easonlao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-system
Source: https://github.com/easonlao/jiazi-game/tree/main/.claude/skills/design-system
Command: npx skills add https://github.com/easonlao/jiazi-game --skill design-system-easonlao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents slow, inconsistent game design documentation by guiding you through writing a complete GDD for one system using existing project context and dependency awareness.

Core Features & Use Cases

  • Guided, section-by-section GDD writing: prompts you to author Overview, Player Fantasy, Rules, Formulas, Edge Cases, Dependencies, Tuning Knobs, and Acceptance Criteria in sequence.
  • Context-aware and dependency-safe: reads the game concept, systems index, entity registry, and relevant GDDs to ensure your design respects established cross-system facts.
  • Incremental retrofit support: detects which sections are missing or placeholder-only in an existing GDD file and fills only the gaps without overwriting complete content.

Quick Start

Use /design-system movement to generate an informed, incremental GDD for the movement system.

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 without contradicting existing systems?

Guide section-by-section GDD authoring while reading the game concept, systems index, entity registry, and relevant GDDs to ensure your design respects established cross-system facts and prevents inconsistencies.

Can I fill in missing sections of an incomplete GDD without overwriting existing content?

Yes, you can retrofit incomplete GDD files by detecting which sections are missing or contain only placeholders, then filling only those gaps incrementally without overwriting your complete content.

What sections should a complete system GDD include?

A complete system GDD should include Overview, Player Fantasy, Rules, Formulas, Edge Cases, Dependencies, Tuning Knobs, and Acceptance Criteria, authored in sequence with explicit approval gates for each section.

How do I map dependencies before writing a system design document?

Map dependencies by performing multi-source reads across the systems index and relevant GDDs, executing feasibility pre-checks and argument resolution to establish cross-system facts before creating the GDD skeleton.

Does context-aware GDD writing support incremental edits and approval gates?

Context-aware GDD writing supports controlled incremental edits and explicit approval gates for each section, performing feasibility pre-checks and argument resolution before moving to the next documented system component.