design-system

Author game system GDD sections with cross-project context and dependency alignment.

Updated May 13, 2026
One-click install
npx skills add https://github.com/FrancisVarga/the-dream-machine --skill design-system-francisvarga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-system
Source: https://github.com/FrancisVarga/the-dream-machine/tree/main/.claude/skills/design-system
Command: npx skills add https://github.com/FrancisVarga/the-dream-machine --skill design-system-francisvarga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents messy, inconsistent game-system design by guiding you through writing a complete GDD section-by-section, while pulling in existing project context, dependencies, and constraints so the system fits the broader game.

Core Features & Use Cases

  • Guided, section-by-section GDD authoring: Creates (or incrementally fills) the required sections for a single game system in a structured order.
  • Context-aware design from your repo: Reads your existing game concept, systems index, relevant GDD dependencies, and any matching registry entities and past consistency failures to keep decisions aligned.
  • Retrofit without overwriting: Detects incomplete or placeholder sections in an existing GDD and only fills the missing parts when you choose retrofit mode.
  • Review-mode workflows: Supports review modes (full/lean/solo) to control whether specialist agents are consulted during drafting.

Quick Start

Use the design-system skill to design the movement system by running: /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 new system without missing dependencies?

Guided section-by-section GDD authoring reads your existing game concept, systems index, and dependency mappings to generate structured sections, ensuring new game systems align with cross-project context and consistency constraints.

Can I fill in missing sections of an existing game design document without overwriting completed content?

Retrofit mode detects incomplete or placeholder sections in an existing GDD file and incrementally fills only the missing parts, preserving your previously written content during game design document updates.

What is dependency mapping in game system design and why does it matter?

Dependency mapping identifies existing GDD constraints and cross-project context required for a new system. Enforcing dependency-aligned consistency prevents messy design by ensuring your system fits the broader game architecture.

Does the GDD authoring process support solo game designers or do I need a full team?

Review modes control specialist involvement during GDD drafting. You can select full, lean, or solo modes to manage whether specialist agents are consulted, supporting both team-based and independent game design workflows.

What's the best way to ensure engine feasibility when authoring a game system GDD?

Context-aware GDD authoring reads available engine feasibility docs alongside core concept files before generating section skeletons. This validates that your game system design aligns with technical constraints early in the drafting process.

Why does my game system design become inconsistent across multiple GDD files?

Inconsistency occurs when GDD authoring ignores cross-project context and past consistency failures. Parsing relevant registry entities and dependency mappings before drafting enforces dependency-aligned consistency across your game design documents.