Define the Adhesion route
A wall-running prompt should state how the character attaches, what surface supports the move and when grip runs out. Adhesion is a fictional twelve-cell course with two continuous wall sections and a finite grip resource. The runner starts at cell 1, and the exit is at cell 12.
Wall one runs beside route cells 3–5; wall two runs beside cells 8–9. Step moves one open floor cell. Attach is legal only when the runner is next to a continuous wall. While attached, WallRun advances exactly one route cell along that same surface and costs one grip. Grip starts at five and cannot be negative.
At the end of each wall section, JumpOff detaches and lands on the next defined open floor cell: cell 6 after wall one and cell 10 after wall two. An ordinary Step cannot cross the wall gap. The course is completed by reaching cell 12 within sixteen actions.

Keep contact and grip state visible
The runner's state should show current cell, attached wall ID, grip and whether a landing tile is open. WallRun is unavailable if the runner has detached, the wall segment ends, the next route cell is unsupported or grip is below one. JumpOff is legal only at the end of a wall section with the defined landing open.
If grip reaches zero while attached before the route is complete, the run fails. The design does not add midair drift or a second jump. Restart restores cell 1, five grip, no wall attachment and the action counter.
This makes the wall-run a bounded traversal state rather than a generic animation. A future physics version can add momentum after the simple contact, cost and landing checks have been inspected.

Trace the example
Step from cell1 to cell2, then Attach to wall one. WallRun through cells3, 4 and 5, spending three grip (5→2). JumpOff to open floor cell6. Step to cell7, Attach to wall two, then WallRun through cells8 and9, spending the remaining two grip.
JumpOff to cell10, then Step through cells11 and12. The route uses thirteen actions including two attaches, two jump-offs and the floor steps, so it is within the sixteen-action limit. All five grip points are spent only while supported by the two continuous wall sections.
This is a fictional route trace, not a tested platformer run. A build should log wall ID, contact cell, grip before/after and landing occupancy for every traversal action.

Write the six prompts
Use one prompt per design decision so later checks have a clear source of truth. These drafts describe Adhesion; they have not been run and do not represent a generated playable game.
Prompt 1: place course and wall spans
Create a 12-cell route with start1 and exit12. Put continuous wall surfaces beside cells3–5 and8–9. Set grip5 and action limit16. Mark landing cells6 and10 open.Prompt 2: define attachment
Step moves one open floor cell. Attach is available only adjacent to a continuous wall. Show wall ID and attachment state.Prompt 3: resolve wall-run drain
WallRun moves one route cell along the attached surface and spends1 grip. Reject if wall ends, support is missing or grip<1; do not move or spend on rejection.Prompt 4: set jump-off landings
JumpOff detaches only at a wall-section endpoint and lands on its defined open cell: 6 after first wall, 10 after second. Ordinary Step cannot cross wall gaps.Prompt 5: define win/failure/reset
Win at cell12 within16 actions. Fail if limit expires or a WallRun is attempted without grip. Restart restores start, grip, attachment and action count.Prompt 6: prepare future checks
For future checks log cell, wall ID, support, grip, attachment, landing and action count. Check attach range, continuous wall, exact drain, end-of-wall release, blocked landing, route, timeout and Restart. Do not claim unobserved tests pass.SEELE’s official page describes general plain-English prompting, a playable first version, browser testing and refinement; it does not verify Adhesion. See Free AI game maker for workflow context only.
Prepare future build checks
Capture route cell, support wall, grip and attachment state for every move. Test a continuous run, a broken wall, zero grip, a blocked landing, both jump-offs and the sixteen-action finish limit. These are future checks, not passed tests. Record the before and after state so a later build can be compared with the specification.
| Future check | Expected rule | Evidence to capture |
|---|---|---|
| Attach | Only adjacent to wall | Player cell and wall ID |
| WallRun | One supported cell per grip point | Support and grip delta |
| Wall end | Reject run beyond continuous surface | Wall span and position |
| JumpOff | Land on specified open cell | Landing occupancy and attachment |
| Route/reset | Reach exit by action16; restore grip on reset | Goal and state snapshot |
No real game run, browser test or measured result is available for this fictional example. The illustrations are original concept art and are not screenshots.
Frequently asked questions
What should a wall-running game prompt specify?
Define attach range, continuous surface requirements, movement distance, grip cost, release and landing behavior.
How much grip does Adhesion start with?
The fictional route starts with five grip points and spends one per supported WallRun cell.
Can the runner WallRun after leaving the wall?
No. WallRun requires an active attachment to the same continuous wall segment.
Were these wall-running prompts tested in a playable game?
No. Adhesion is a fictional route example, not observed gameplay.
Where does JumpOff land?
It lands at cell6 after the first wall and cell10 after the second, if those cells are open.


