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:

1. Interactive Socratic Interview (/grill-me): When starting a new game project or refining an idea, activate the /grill-me interview workflow (asking targeted, one-at-a-time probing questions) to systematically explore each branch of the game design tree.
2. 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").
3. 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.
4. Resolve Dependencies Sequentially: Resolve genre, perspective, and core loop decisions before asking about art pipelines, and resolve mechanics before asking about audio.
5. Produce Authoritative GDD.md: Synthesize all agreed decisions into a structured GDD.md saved in the workspace root using references/gdd_template.md.