design-system

Guide section-by-section game design document authoring with YAML frontmatter and no-overwrite editing.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/dnkrow/skill --skill design-system-dnkrow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-system
Source: https://github.com/dnkrow/skill/tree/main/claude-global/design-system
Command: npx skills add https://github.com/dnkrow/skill --skill design-system-dnkrow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It streamlines writing a complete, consistent game design document (GDD) for a single game system by guiding you through every required section while pulling in existing context and dependency constraints.

Core Features & Use Cases

  • Argument-driven guided GDD creation: Design a new system or fill gaps in an existing GDD using modes like lean/full/solo, with predictable section coverage.
  • Context-first consistency: Reads the game concept, systems index, relevant registries, dependency GDDs, and past failure patterns to reduce contradictions and missed interfaces.
  • Retrofit-safe incremental editing: Detects missing or placeholder-only sections and fills only what’s incomplete without overwriting existing content.
  • Section-by-section workflow with approvals: Walks through overview, fantasy, rules, formulas, edge cases, dependencies, tuning knobs, and acceptance criteria, using structured user approvals.

Quick Start

Use the design-system skill to generate a complete GDD for your next system by running the command: /design-system movement

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 without missing dependencies?

To retrofit a game design document (GDD), you detect missing or placeholder-only sections and fill only what is incomplete. This incremental editing approach honors a strict no-overwrite rule, ensuring existing content remains untouched while gaps in the design are safely populated.

What is the best way to ensure consistency across multiple game design documents?

Ensuring GDD consistency requires cross-referencing the game concept, systems index, and dependency GDDs before authoring. By pulling past failure patterns and registry facts into the writing process, you reduce contradictions and missed interfaces across system architectures.

Can I add YAML frontmatter to a system GDD for automated discovery?

Yes, adding YAML frontmatter with discovery fields to a system GDD supports automated context gathering and review mode. This metadata allows argument parsing for retrofit detection and guided authoring workflows to identify missing sections accurately.

What sections should a complete game design document include for system architecture?

A complete GDD for system architecture should include overview, fantasy, rules, formulas, edge cases, dependencies, tuning knobs, and acceptance criteria. A section-by-section workflow with structured user approvals ensures each required area is thoroughly documented.

Do I need an existing systems index before authoring a new system GDD?

You need an existing systems index and relevant registries before authoring a new system GDD to maintain context-first consistency. Reading dependency constraints and past failure patterns from these sources prevents contradictions and missed interfaces during the design process.