game-design-review

Use when a user asks to improve browser game design, roguelike systems, reward loops, enemies, progression, character roles, build choices, event choices, or player onboarding. Blocks balance claims a

SKILL.md

GitHub

Game Design Review

Review the game as a playable system.

Core Questions

  • What is the player trying to do right now?
  • What choice matters?
  • What feedback proves progress?
  • What risk creates tension?
  • What recovery path prevents frustration?
  • What system depth appears after the first simple action?

Review Axes

  • core loop clarity;
  • reward pacing;
  • build choice quality;
  • enemy counterplay;
  • failure and recovery;
  • roguelike replay value;
  • UI cost of added complexity;
  • originality without copying external games.

Evidence Rules

Balance claims require before/after, repeated runs, paired outcomes, or clear numerical evidence.

External references can inspire borrow patterns, but do not copy code, assets, names, or proprietary content.

Output

Return:

  • strongest design opportunity;
  • biggest player-risk;
  • evidence missing;
  • safe proposal;
  • approval gates before runtime work.