platformer

1# Platformer
2 
3A playbook for 2D platformers — the run/jump controller "feel", level structure, hazards,
4and goals. This is a **compositional** skill: it wires an engine movement skill, a tilemap
5skill, and design skills into a working game. It does **not** re-teach physics or tilemaps;
6it tells you what to build and how to make jumping feel good.
7 
8## When to use
9 
10- Use when building a side-scrolling or single-screen platformer, a "Mario-like" /
11  "Celeste-like", or any game whose core verb is **jump between surfaces**.
12- Use when a jump feels floaty, unresponsive, or "unfair" and you need feel fixes
13  (coyote time, jump buffering, variable height, corner correction).
14 
15**When *not* to use:** top-down movement with no gravity → use the engine movement skill
16directly. 3D first-person traversal → `fps-shooter`. Grid/turn movement → `roguelike`.
17For the raw kinematic body API, use `godot-2d-movement` (or your engine's controller skill).
18 
19## Core loop
20 
21**Observe a gap/hazard → commit to a jump or move → land safely (or die) → reach the next
22checkpoint/goal.** A platformer lives or dies on the *moment-to-moment* feel of that single
23jump, repeated thousands of times. Tighten the controller first; everything else is content.
24 
25## Must-have systems
26 
271. **Run/jump controller** — horizontal accel/decel, gravity, jump, with the feel aids below.
282. **Solid + one-way collision** — ground, walls, and "jump-through" platforms.
29…