# Reject All

Ten levels of increasingly evil cookie banners.

Category: Game with a score

## The brief

Make a comedic browser game whose only goal is to reject all cookies. Build 10 levels of escalating consent-banner dark patterns (fleeing buttons, guilt-trip copy, fake close icons, hundreds of toggles, nested "legitimate interest" menus, and worse), each beatable in under 30 seconds once you figure it out. Time the whole run, and end with a share card (a downloadable PNG plus copyable text) showing the total time and the nastiest level. Use fictional company names only.

## The exact prompt every model received

````markdown
Make a comedic browser game whose only goal is to reject all cookies. Build 10 levels of escalating consent-banner dark patterns (fleeing buttons, guilt-trip copy, fake close icons, hundreds of toggles, nested "legitimate interest" menus, and worse), each beatable in under 30 seconds once you figure it out. Time the whole run, and end with a share card (a downloadable PNG plus copyable text) showing the total time and the nastiest level. Use fictional company names only.

## House rules (identical for every model)

- Build a website in `./site/`. The entry point is `./site/index.html`. Only `./site/` gets published, so keep scratch files, scripts and tooling outside it.
- It must be fully static: no backend, no server code, no API keys, no logins. It will be served as plain files from a CDN under a sub-path and shown inside an iframe, so use relative URLs only.
- JavaScript libraries and web fonts from public CDNs are fine (cdn.jsdelivr.net, unpkg.com, cdnjs.cloudflare.com, esm.sh, Google Fonts). Nothing else may be fetched at runtime.
- Resources: you may create any media the site needs (images, textures, audio, video, 3D models, data files) and put them in `./site/`. Make them yourself with code or local tools: node, python3 and ffmpeg are installed, and you may `npm install` packages into a folder outside `./site/`. Do not download third-party media. Budget: 40 MB total, 15 MB per file.
- It must work with mouse, keyboard and touch, on screens from 375 px phones to wide desktops, and run smoothly on a mid-range laptop.
- The first 3 seconds matter: it should look impressive immediately.
- Test it. Run `node .prism/check.mjs`: it opens `./site` in a real headless Chromium at desktop (1440×900) and phone (390×844) sizes, prints console errors and failed requests, and saves screenshots to `./.prism/shots/`. Look at the screenshots. Run it as often as you like.
- Work autonomously; nobody will answer questions. You have up to 60 minutes.
- When you are done, write `./NOTES.md` (outside `./site/`) covering what you built, your key decisions, and known issues.
````

## Artifacts

- **Haiku 4.5** (`claude-haiku-4-5-20251001`, 3m 50s): live https://prism-artifacts.berrocal.xyz/reject-all/haiku-4-5/site/index.html · replicate https://prism.berrocal.xyz/i/reject-all/haiku-4-5/index.md · pack https://prism-artifacts.berrocal.xyz/reject-all/haiku-4-5/pack.zip

Input resources: none