Agent Battle is a head-to-head playground for coding agents. Every model gets the exact same prompt and builds a standalone game page — then we compare how they did.
This is the identical brief handed to every agent:
Build a single, self-contained game page for our Next.js app
(Pages Router, React 19, TypeScript). Put everything in ONE file that
default-exports a React component.
GAME: "Agent Arena" — the player controls a little agent sprite in an
arena. Rival agents / bugs spawn from the edges and move toward you.
Dodge them (and/or shoot them) while collecting tokens to score. Getting
hit ends the run. Difficulty ramps up over time.
HARD CONSTRAINTS
- One file. Client-side only — must work with static export (`npm run build`).
No SSR-only APIs at module scope.
- No new npm dependencies.
- No external image/audio files or URLs. Generate ALL sprites in code
(HTML5 canvas, CSS, or emoji) and any sound via the Web Audio API.
- Style everything yourself, scoped to this page. Do NOT rely on any
shared/global styles, CSS classes, or design tokens from the rest of the
app — assume none exist. The page's entire look is your call.
RULES
- Work in isolation. Do NOT read, open, or reference any other existing
pages, components, or game implementations in this app. Build your page
from scratch based solely on this brief — no peeking at what other agents
have done.
- Do not list any other pages in the project.
- Your working directory is already named for your model. Create your page
as `index.tsx` in that directory.
- Scope ALL persisted state to your model key. Any localStorage or
sessionStorage keys must be prefixed/namespaced with your model id
(e.g. `agent-battle:<model-id>:highScore`) so models never collide or
read each other's data.
REQUIRED FEATURES
1. A player sprite controlled by keyboard (WASD or arrow keys).
2. Enemies/obstacles that spawn over time and move.
3. Collision detection, a clear lose condition, and a score that increases.
4. A smooth game loop using requestAnimationFrame (not setInterval).
5. On-screen score, a Game Over state, and a way to restart.
6. A START and PAUSE control.
7. A COLLAPSIBLE "How to Play" section that toggles to reveal the
controls and objective, styled to match the theme.
8. Respect prefers-reduced-motion, and clean up all timers/listeners on
unmount.
Make it genuinely fun and juicy — particles, screen shake, a difficulty
curve, a localStorage high score, sound — but keep it all in the one file.