2D Games

A real core loop with an objective, escalating difficulty, score, win and lose states, start and restart, and a session high score; keyboard and touch controls; and synthesised sound effects with a mute control. It is one self-contained HTML file with no outside libraries. Before you see it, the game is opened in a real browser and played end to end — start, score, a run that ends, and a restart — and repaired if that fails. The playthrough proves the game can be played and ended; it does not prove it can be won.

Built on the Sandbox engine. These are the stages it runs, in order — the same list the builder shows live while it works.

1. 1BriefCode

   Picks the genre from the words in the prompt and fixes the core loop, the goal and both endings before any inference runs.

2. 2ArchitectureCode

   Names the states, the entities and the systems the runtime has to own, plus the delta-time rule the loop must obey.

3. 3Level designCode

   Fixes the world shape, the spawn cadence and the difficulty curve — what rises, by how much, and against what floor.

4. 4Gameplay systemsCode

   Decides scoring, progression and the feedback that makes both legible during play.

5. 5AssetsCode

   Plans what is drawn and what moves while it is drawn, and synthesized audio — nothing fetched, since the sandbox blocks it.

6. 6PhysicsCode

   Chooses the collision model the genre actually needs — boxes, squared-distance circles or grid cells — and names the tuning constants.

7. 7GenerateAI call

   One tool call, briefed with the plan above, returning a complete self-contained HTML document containing the whole game.

8. 8Runtime testCode· a browser can be launched — reported as skipped when it cannot

   Opens the game in a real browser, taps and presses it, and watches for two seconds.

9. 9PlaythroughCode· the game labels its state — reported as skipped when it does not

   Starts the game, plays it for six seconds, watches a run end without input, then presses Restart and checks it comes back.

10. 10QA auditCode

    Reads the emitted document for the things that would make the game unplayable or dead on arrival.

11. 11RepairAI call· the runtime test or the QA audit found something worth an edit

    One targeted pass carrying every failing runtime check and every repairable audit finding together.

12. 12Re-testCode· a repair ran

    Audits the repaired document, so the repair is measured rather than assumed.

13. 13Final validationCode· a repair ran

    Plays the repaired game in a browser, because a repair that satisfies every source rule can still throw.

14. 14Keep or discardCode· a repair ran

    Scores both versions on the audit and the runtime failures together, and keeps the repair only if it measured better.

• Refine in its builder — “make the enemies faster after level 3”.
• Share the link; it plays in any modern browser, on desktop or phone.

It runs in a sandboxed frame with no network access, so there are no online leaderboards or saved progress between visits.