game-design

Invoke the game-design skill with an optional target argument (cookie, factory, rpg, or all). It reads the game's state.rs, logic.rs, actions.rs, and render.rs files, then diagnoses core loops, tension, growth, and replayability using a structured framework.

The skill produces proposals formatted with fun rationale, implementation overview pointing to specific files, implementation cost, and priority. It ends with a roadmap ordering all proposals by maximum fun improvement per unit of effort.

Yes, pass the target argument with a game name such as cookie, factory, or rpg to limit analysis to that game's directory. Omitting the argument or passing all analyzes every game in the project.

Yes, all proposals respect the project's constraints: CLI/TUI interface, Rust plus WASM, 10 ticks per second, and touch support. Suggestions leverage text-based strengths like high information density and ASCII visual feedback.

The analysis is grounded in code structure and design heuristics, so it cannot measure actual player emotion or playtest behavior. Quantitative critique metrics from the test suite help, but human playtesting remains necessary for validation.