This skill treats a level as a sequence of intended experiences delivered through space. The order it follows: measure the character, block out with primitives, check reachability and pacing, collect playtest reports, then dress the level.
It includes three Godot 4.7 patterns: a headless script that measures the real jump of the game’s player scene, a pacing check over a list of beats, and a reachability search over a room graph that tracks which keys and abilities the player holds.
What You Get
- A headless jump measurement that reports apex, reach and airtime from the real player scene
- A sizing rule: required gaps at about 0.7 of measured reach, optional challenges near 0.95
- A pacing check that flags too many high-intensity beats in a row, a missing rest before the climax and a level that does not open with a teach beat
- A goal_reachable search over a room graph that finds soft-locks such as a red key that no room grants
Common Use Cases
- Sizing gaps and ledges from the controller’s measured jump, with the formula as a first estimate only
- Planning a critical path, optional branches and gating order for a metroidvania
- Finding a soft-lock before any art is made
- Reviewing a level that bores or confuses playtesters with specific questions
What Makes It Unique
The metrics come from running the game’s own player scene: with the example constants, the ideal arc gave 90 px and 206 px while the measured values were 93.6 px and 212 px. The reachability check tracks held keys, so it catches a key behind its own door that a simple connectivity flood fill would pass. It also tells the agent to ask the user for specific playtest reports, because it cannot watch players.
Under The Hood
The skill is instructions and one reference file on pacing and flow, with no scripts of its own. It tells the agent to write helper scripts and run them with Godot in headless mode: one instantiates the project’s player scene on a generated floor and presses input actions to measure the jump, and others run the pacing and reachability checks in the project’s headless test runner. It also mentions baking prototype geometry into static resources. It does not fetch web pages or call APIs.