Build a coach
for your next landing.
Make a lander-coach folder and copy your working HTML file into it. Open that folder in the agent and ask it to edit this copy using the brief below. Your original stays in its first folder. The change turns the landing challenge into a lesson.
Edited build brief
Keep the original physics, landing conditions, one-file format and accessible flight controls. Reframe the program as a teaching instrument for a first-time player. Let the reader choose a vertical-drop scenario, pause and advance one physics step, and see velocity and thrust directions. After touchdown, explain which landing conditions passed or failed and offer a replay of the final five seconds. Keep a quick restart. Verify that the explanation and replay agree with the actual flight.
How it feels
The reader gets a coach that makes each landing understandable and gives the next attempt a clear goal.
What the agent needs to build: interface
Scenario choice selects a starting flight. A step button advances one calculation while paused. Direction arrows and an after-flight explanation make the journey choose, try, inspect and retry.
What the agent needs to build: structure
The agent needs one reusable motion calculation, a record of the current flight and a short list of recent flight records for replay. The debrief must use the same pass/fail landing test as the game. That keeps the explanation tied to what happened.
Acceptance check
Ask the agent to set up a repeatable gentle contact outside the pad. The explanation should identify position as the failure. Then try a flight: step and replay must agree with the recorded flight.
Design exercise: try a new build from this edited brief. Status: proposed; implementation and testing pending.