Build a playable game (you pick the concept)

the prompt

Build one playable browser game that demonstrates the absolute ceiling of your game development capability. You choose the game. That decision is part of what's being evaluated. Context you should know: this is going into a video comparing you against other frontier models, shown to a large audience, and your work will be credited to you by name. Every model gets this exact prompt. So go nuts and show people what you're actually capable of. Requirements: 1. **You pick the game.** Any genre, any style, original or your own take on something. Decide and commit. Another Pong, Snake, or Flappy Bird clone is a wasted turn — the ambition of what you attempt is part of the score. 2. **It has to be genuinely fun within thirty seconds.** No tutorial wall, no menu maze. It's playable the moment it loads, and the core loop should be clear and satisfying almost immediately. This is the single most important requirement. 3. **The graphics bar is high.** This should look like a real game someone would ship — incredibly realistic, or at minimum a deliberate, fully-realized art direction executed to a professional standard. Untextured primitives, flat-shaded blobs, and programmer art are failures regardless of how good the mechanics are. Lighting, materials, effects, and readability all count. 4. **Depth is the point.** Pull from whatever best showcases you — including but not limited to: a tight core loop with real progression, game feel and juice (screenshake, hitstop, easing, impact particles, camera punch), enemy AI and behavior systems, pathfinding, physics, procedural generation, a difficulty curve that actually escalates, upgrade or build variety, hundreds of simultaneous entities without frame drops, procedural audio via the Web Audio API, a designed HUD and menu system, art direction with a coherent visual identity, replayability. 5. **You have free reign to look up how to use any of these**, and to add any other technique you think demonstrates more. The list is a starting point, not a boundary. 6. **Single self-contained `index.html`.** Any library via CDN. No build step, no server, no API keys. Keyboard and mouse controls, explained on screen in one line. 7. **No hotlinked sprites or audio files, but you may pull in open source libraries freely** — engines, physics, procedural generation, noise, asset generators, particle systems, anything on a CDN. Generate art procedurally, author it in canvas/SVG/WebGL, or use library-driven generation. Sound should be synthesized via the Web Audio API. You have free reign to look up what libraries exist and how to use them. 8. **QA it by actually playing it.** Play several full runs. Confirm the loop works, difficulty scales, nothing softlocks, collisions are honest, and the frame rate holds when the screen gets busy. Fix what breaks.

…