unity-gameplay
Installation
SKILL.md
unity-gameplay — a genre is a set of constraints, and the constraints pick the skills
A genre name decides nothing you can build from. "Platformer" does not say who owns the transform, what the level unit is, or which clock the camera reads. Six constraints do, and two games with the same label and a different transform owner share no controller code — while two with different labels and the same six share almost all of it.
Request → where to go
| The request | Go to |
|---|---|
| "make a platformer", "build a top-down shooter", "which skills for a tactics game" | §0, then the genre file it names |
| "add a player character" | §0, then the controller row in Load what the situation needs |
| "how wide can the gap be", "the jump cannot reach the ledge" | Discipline (numbers before levels) and reference/level-metrics.md |
| "what do we build first", "is the prototype done" | reference/pipeline-stages.md |
| The idea, the brief, the look, a preview before code | unity-game-brief |
| Controls · camera · Animator work | unity-input · unity-camera · unity-animation |
| Any other system a game needs | Load what the situation needs |