Kitchen Derby — tiny kitchen objects, giant countertop, full contact racing
Pressure cookers, forks and coffee mugs race across a giant kitchen counter.
Drift for boost, grab one weapon, shove your rivals off the counter.
3 laps, under 2 minutes, plays in the browser with no install.
Tech stack
- Gemini (4 Argon)
- Vercel
- Google AI Studio (4 Argon)
Links
Prompt steps
Step 1
Build a single self-contained HTML file called index.html: a 3D kart racing game called Kitchen Derby. No build step, no bundler, no npm. Use Three.js r160 from a CDN. Everything else must be vanilla JavaScript inside the same file. SETTING Tiny kitchen objects race across a giant kitchen countertop. The player is a red pressure cooker kart, 2.7 units long, on four fat wheels. REQUIREMENTS FOR THIS STEP ONLY 1. A closed racing circuit built from points, generated as a smooth road mesh with red and cream kerbed edges. It must have one long straight and gently curved corners, no hairpin tighter than a 20 unit radius. 2. One drivable kart with arcade physics: acceleration, braking, drag, lateral grip, and steering that is strong at low speed and slightly weaker at high speed. 3. Steering must feel responsive but never twitchy. Turning rate between 2.2 and 2.8 radians per second. The kart must go where its nose points, not slide wide. 4. A chase camera that follows the kart's heading smoothly, pitched 36 degrees down, field of view 60, never orbiting on its own, never clipping the kart out of frame. 5. Driving off the road slows the kart but must never stop it dead. Hitting the outer edge must slide the kart along the edge, not kill its speed. 6. Show a small on-screen key monitor that lights up when W, A, S, D, Space and Shift are pressed, plus a speed readout in km/h. CONTROLS W accelerate, S brake and reverse, A and D steer, Shift drift, Space use item, R restart. QUALITY BAR Runs at 60 fps in Chrome on a laptop. Fixed timestep physics at 60 Hz, decoupled rendering. Code must be readable, with a single TUNING object at the top holding every gameplay number so it can be tuned later. Do not add enemies, weapons, menus or sounds yet. Only the drivable core. After writing the file, list every tuning value you exposed and what a higher or lower number doesStep 2
Extend the same index.html file. Keep all existing physics, camera and tuning values. Do not change the feel of the kart. ADD THREE AI RIVALS 1. One is a white coffee mug kart, one is a steel fork kart on three wheels, one is a dark blender kart. Build all four karts from simple geometry only, no external models. Each must have a different silhouette, not just a different colour. 2. AI follows the racing line using a look-ahead point on the track curve, plus a personal lane offset so they do not stack. AI must slow for sharp corners and use drift on the tightest ones. AI must be beatable but not passive. ADD COMBAT 3. Weapon crates on the track at eight positions. Driving over one gives exactly one random item: steam blast, oil slick, speed boost, or shield. One item slot only, shown in the HUD. 4. Kart against kart collisions must feel heavy: impulse of at least 15 units, a slight spin on glancing hits, and camera shake. A hard hit should visibly throw the rival off line. 5. Steam blast: a short cone in front that pushes rivals backwards. Oil slick: a puddle that makes rivals slide. Boost: 1.7 seconds of extra top speed. Shield: 3.5 seconds of immunity. ADD RACE STRUCTURE 6. 3 laps, starting grid of 4, a 3-2-1 countdown, live position indicator, lap counter, race timer, and a results screen listing finish order and times. 7. Pressing the arrow keys at any time turns the second kart into a human player for local 2 player. Until then it is driven by AI. QUALITY BAR Every number lives in the same TUNING object at the top. No magic numbers inside functions. After writing, summarise how collisions, item pickup and lap counting are implemented, and name the three riskiest bugs you would expect in this code.Step 3
Extend the same index.html file. Do not change any physics values. ART DIRECTION — kitchen scale 1. Counter surface: warm wood colour with a subtle grain pattern, black tyre skid marks behind karts, and scattered bread crumbs as small instanced props. 2. Landmarks that sell the scale: a coffee mug as tall as a building beside the track, a giant spoon used as a ramp, a folded checkered notebook forming a narrow bridge. Low-poly, chunky, matte materials, roughness 0.7. 3. Lighting: warm morning sun from one side with soft shadows, plus a cool sky fill. Background kitchen softly faded with fog so the track always reads clearly. 4. Palette locked to: wood #C8A278, counter cream #E8DFD0, cooker red #D93A2B, ceramic #F5EFE6, steel #9AA3AB, oil #E0A93B, sky #BFE3FF. HUD 5. Flat vector style, cream panels #F5E7C8 with 5 pixel navy outlines #1E2350 and rounded corners. Top left: character circle portrait, 3 hearts, one item slot. Top right: two large digits for position and lap. Bottom centre: speed. 6. Numbers only in the HUD. No long words. Everything must be readable on a phone screen at arm's length. FEEL AND SOUND 7. Wheel dust particles when drifting, a small squash animation on impact, and a slight camera roll of about 2 degrees when cornering. 8. Sound with the WebAudio API only, no audio files: a low engine hum whose pitch rises with speed, a click for item pickup, a thud for collisions, and a short jingle on finishing. Everything must start only after the first user interaction, and muting must be one click. QUALITY BAR Stay under 4 MB total including Three.js from CDN. Keep draw calls low with instancing for repeated props. After writing, list every asset you generated procedurally and confirm there are no external image files.Step 4
Extend the same index.html file. This step is only about making it shippable and instantly shareable. Do not add new gameplay. FIRST IMPRESSION 1. A title screen that appears in under 1 second: big logo "KITCHEN DERBY", one line of subtitle, and one large PLAY button. Behind it, the game must already be rendering and idling so it never looks like a loading screen. 2. One tiny tutorial line on the title screen only: WASD to drive, Shift to drift, Space to use an item. Nothing else. 3. Press Space or click PLAY starts a race immediately, no menus, no account, no settings. THE 15 SECOND HOOK 4. Make sure something delightful happens in the first 15 seconds of a fresh race without the player doing anything special: a rival should be visible immediately, a weapon crate should be within reach in the first 3 seconds, and the giant coffee mug landmark must be in frame in the opening shot. 5. On finishing a race, show a share card in the HUD area: your time, your position, and a one line result. Add a button that copies a short text summary to the clipboard. MOBILE AND ROBUSTNESS 6. Touch controls: a left virtual joystick for steering, a right button for accelerate and a second button for the item. They must appear only on touch devices. 7. Handle window resize, handle lost WebGL context with a friendly message, and pause the simulation when the browser tab is hidden. 8. Cap the pixel ratio at 2. Never allocate objects inside the render loop. QUALITY BAR The whole thing must be one file that works when opened directly from disk, with no server, no build and no external assets other than the Three.js CDN script. After writing, give me a 10 line checklist of what a reviewer should click to verify it works, and confirm the file size
9 likes · 8 comments · 20 views
Comments (4)
This is a really fun game Anita. You did a nice job again as you always do. Good promots also I liked seeing the progression. Great job!
thanks sir
really fun, In my opinion, Argon 4 is indeed good for game development. I’m going to give it a try as well.
thanks cassy .,
This is fun! Add more circuits.
thanks u sasam
nice idea anita you can, it has the potential to grow more<div><br></div>
thanks mate