game-design

Prototype the core loop first and validate it against the patterns in references/patterns.md before adding systems. The Skill prioritizes fun and a polished core loop over feature completeness, since scope creep kills more games than technical debt.

The guidance applies to Phaser, Unity, Unreal, and Godot, as well as general game development topics like sprites, collision, physics, tilemaps, and game loops. Engine-agnostic principles like performance and player experience are emphasized throughout.

Consult references/sharp_edges.md, which lists critical failures and why they happen, including frame rate and physics issues. The Skill treats frame rate as a feature, so performance problems are diagnosed as player-experience risks, not just technical bugs.

Yes, it validates design inputs against references/validations.md, which contains strict rules and constraints. If your request conflicts with the reference guidance, the Skill corrects it using the documented information rather than generic opinion.

Playtest early, often, and with fresh eyes, according to the Skill's core principles. Testing the prototype of the core loop before building additional systems prevents wasted effort on mechanics that do not serve the player experience.