Click a card to play
All tests were run using OpenCode. Every model was given 256k context at Q8_0 quantization, except BF16 models which ran at full precision.
In Plan mode, send this exact prompt:
Create a comprehensive plan for this task:
Build a 3D racing game in a single HTML file using Three.js from a CDN.
The game must include:
- A car the player controls with WASD or arrow keys — acceleration, braking, and steering
- A visible track with boundaries the car cannot pass through
- A camera that follows behind the car
- A lap counter that increments when the player completes a loop
- A speedometer or speed readout visible on screen
- The game should start immediately on page load with no menu required
Technical requirements:
- Do not use any dependencies other than Three.js from cdnjs
- Everything must work by opening the HTML file directly in Microsoft Edge
- The game loop must be tied to a fixed timestep, not raw frame rate — it must run at the same speed on a 60Hz and 165Hz monitor
Do not use any dependencies other than Three.js from cdnjs. Everything must work by opening the HTML file directly in a browser.
Note: Claude wrote the above prompt. I never read it — blame Claude if you don't like it.
Switch to Build mode, enable Playwright MCP, then send:
Yes implement it. After you are finished thoroughly analyze your implementation for any bugs or errors. Then use Playwright MCP to check for any bugs in the browser.
Run the HTML output in a browser. Play the game and describe any issues you encounter — for example: "Steering is backwards when driving forward but correct when reversing" or "All I see is a black screen." No hints — just describe what you see. The one exception is you may tell the LLM if the track is a bland donut/circle.
If there are 2 or fewer bugs/visual issues on any of the 3 turns, back up the whole folder, report the issues, then add: "Improve the game in any way it deems fit." All 3 turns are always used.