← ClaudeAtlas

unity-gameplaylisted

START HERE for any gameplay request: make a platformer, runner, top-down or tactics game, add a player. Reads 2D or 3D and the view, routes each system; level metrics, stages.
tipoLi5890/unity-dev-skills · ★ 2 · AI & Automation · score 75
Install: claude install-skill tipoLi5890/unity-dev-skills
# 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* | | Constraint | Values | What it picks | |---|---|---| | Dimension | 2D · 3D | The physics vocabulary, and every component name after it | | Projection | orthographic (size, pixels per unit) · perspective (FOV, distance, pitch) | Camera rig, sorting, pixel snapping | | View | side · top-down · isometric · behind the c