game-design
Interactive game design workflow and Game Design Document (GDD) authoring guide for 2D games. Structures game ideation through interactive probing interviews, defining core gameplay loops, win and loss conditions, control schemes, visual asset pipelines, and audio strategies into a clean GDD.md. Activate when conceptualizing a new game, defining gameplay mechanics, conducting game design interviews (/grill-me), or authoring a Game Design Document.
Daniela Petruzalek (daniela@danicat.dev) · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add danicat/skills --skill game-design技能说明
name: game-design description: > Interactive game design workflow and Game Design Document (GDD) authoring guide for 2D games. Structures game ideation through interactive probing interviews, defining core gameplay loops, win and loss conditions, control schemes, visual asset pipelines, and audio strategies into a clean GDD.md. Activate when conceptualizing a new game, defining gameplay mechanics, conducting game design interviews (/grill-me), or authoring a Game Design Document. license: Apache-2.0 metadata: category: game-dev tags: "gdd, mechanics, game-dev, prototyping" author: Daniela Petruzalek (daniela@danicat.dev) version: "0.3.0" catalog: https://skills.danicat.dev
Game Design & Interactive GDD Creation Guide (Game Designer Role)
This skill equips AI agents acting in the Game Designer Role with structured Socratic interview protocols, probing frameworks, and templates to guide users from initial 2D game ideas to a production-ready Game Design Document (GDD.md).
[!IMPORTANT] 100% Genre-Agnostic 2D Design Principle: Never assume a 2D game uses side-scrolling gravity or platforming physics. This workflow supports every 2D game genre, including Top-Down RPGs, Bullet-Heavens / Auto-Shooters, Twin-Stick & Vertical/Horizontal Shmups, Turn-Based Tactics, Roguelike Deckbuilders, Grid & Physics Puzzle Games, Visual Novels & Narrative Adventures, Rhythm & Arcade Games, and Side-Scrolling Platformers / Metroidvanias. Always tailor spatial, simulation, control, and asset questions to the chosen genre.
1. Game Designer Role & Socratic Interview Protocol (/grill-me)
The Game Designer Agent aligns the user's creative and technical vision before any code or assets are generated:
- Interactive Socratic Interview (
/grill-me): When starting a new game project or refining an idea, activate the/grill-meinterview workflow (asking targeted, one-at-a-time probing questions) to systematically explore each branch of the game design tree. - Provide Concrete Recommendations: For every probing question, offer an expert recommendation tailored to the user's chosen 2D genre and Ebitengine runtime (e.g., "Recommendation for a deckbuilder: 640x360 virtual resolution for crisp card typography and hover inspection" or "Recommendation for a retro bullet-heaven: 320x180 virtual canvas with spatial hash collision").
- Explicit Asset Pipeline Selection (Procedural vs. AI vs. Hybrid): Always ask the user to explicitly choose between Pure-Code Procedural (
procedural-art/procedural-composer), AI-Generated Media (nano-banana/lyria), or a Hybrid Pipeline for both visuals and audio. - Resolve Dependencies Sequentially: Resolve genre, perspective, and core loop decisions before asking about art pipelines, and resolve mechanics before asking about audio.
- Produce Authoritative
GDD.md: Synthesize all agreed decisions into a structuredGDD.mdsaved in the workspace root usingreferences/gdd_template.md.
2. Genre-Agnostic Socratic Interview Tree (/grill-me Workflow)
Follow this sequential branching tree when interviewing the user:
Branch 1: Core Concept, Genre & Perspective
├── What is the 1-sentence hook / elevator pitch and primary inspiration?
├── What is the 2D genre? (Top-Down RPG, Bullet-Heaven, Shmup, Turn-Based Tactics, Deckbuilder, Puzzle, Visual Novel, Platformer)
└── What is the camera perspective & spatial topology? (Top-down 2D plane, Isometric/Orthogonal Grid, Card Table/UI Canvas, Dialogue Stage, Side-View Arena)
Branch 2: Simulation Model, Core Loop & Win/Loss Conditions
├── Is simulation Real-Time Continuous (delta-time), Turn-Based / Phase-Driven, Discrete Grid-Step, or Event/Narrative-Driven?
├── What is the primary player loop? (Decision/Action -> Systemic Challenge -> Feedback/Progression)
└── What are the exact quantitative win and loss conditions (or narrative endings)?
Branch 3: Controls & Input Mapping
├── What input devices are targeted? (Mouse/Pointer, Keyboard, Gamepad, Mobile Touch)
└── What are the abstract logical actions? (e.g., Navigate/Move, Select/Primary, Cancel/Secondary, Context/Deck/Inventory, Pause)
Branch 4: Visual Art & Asset Pipeline Strategy (Explicit Choice Required)
├── What is the target visual aesthetic & virtual resolution? (e.g., 320x180 pixel art, 640x360 crisp tactical UI, neon vector)
└── Which Visual Asset Pipeline should we use?
├── Option A: Pure-Code Procedural (`procedural-art`) — zero external image files; code-rendered sprites, vector shapes, particle pools, Kage shaders
├── Option B: AI-Generated Media (`nano-banana` + `sprite-animation`) — sprite sheets, portraits, card art, and tilesets via Nano Banana 2.1
└── Option C: Hybrid Visual Pipeline — `nano-banana` for characters/cards/backgrounds + `procedural-art` for UI, particles, and Kage VFX shaders
Branch 5: Audio & Soundscape Pipeline Strategy (Explicit Choice Required)
├── Which Audio Pipeline should we use for BGM and SFX?
│ ├── Option A: Pure-Code Procedural (`procedural-composer`) — zero external audio files; 16-bit stereo PCM synthesized in memory (6-channel BGM + FM/noise SFX)
│ ├── Option B: AI-Generated Soundtrack (`lyria`) — 44.1 kHz stereo music tracks/loops via Lyria 3.5 (`lyria-3.5` / `lyria-3-clip-preview`)
│ └── Option C: Hybrid Audio Pipeline — `lyria` for studio-quality BGM tracks/loops + `procedural-composer` for zero-latency procedural SFX and UI cues
└── What specific musical mood, BPM range, and gameplay SFX triggers are needed?
Branch 6: Scene Flow, UI/HUD & Persistence
├── What scenes and HUD overlays are required? (Title, Gameplay, Tactical Overlay/Deck View, Dialogue Box, Victory/Game Over)
└── What state persistence or backend integration is needed? (Local save state, run history, or Cloud Run leade
阅读完整来源 ↗