
Opus 4.6
Anthropic · run in Claude Code
- Start to finish
- 10m 18s
- File size
- 28.5 KB
- Lines of code
- 626
What we noticed
- It broke none of the rules we check for.
We gave seven paid models the same landing-page brief and kept what each one wrote. Every page here is real. You can open it.
One brief. The same words, letter for letter, for every model. All seven started at the same moment.
We opened all seven in a browser at 360, 768 and 1440 pixels wide. Every one drew with no errors in the console, and none of them spilled off the side of the screen. Six of the seven also switch to a dark version when the screen asks for one.
This is the whole thing, exactly as each app received it.
Build a landing page. CONTEXT Orrery Systems is a fictional consultancy that designs AI systems for other companies: agent architectures, evaluation harnesses, retrieval pipelines, and the operational plumbing around them. Nine people, based in Lisbon, working remotely. Their line is "We design the systems behind the systems." TASK Write the complete code for a one-page marketing site for Orrery Systems. OUTPUT CONTRACT - Output ONE file of code and nothing else. No explanation, no notes, no commentary before it or after it. - Do not wrap the code in markdown fences. - The file is `app/page.tsx` in a Next.js App Router project. It must be a self-contained, default-exported React function component written in TypeScript. Any helper components, data arrays, and types live in the same file. TECHNICAL RULES - Tailwind CSS v4 utility classes only. No CSS files, no `<style>` tags, no inline style objects unless a utility genuinely cannot express the thing. - No imports except from `react` and `next/*`. No icon packs, no animation libraries, no webfonts from a CDN, no images from a URL. If you want an icon or a graphic, hand-write inline SVG. - It must work as a server component: no "use client", no hooks, no event handlers. Any interactivity comes from plain HTML and CSS (`<details>`, `:hover`, `:focus-visible`, anchor links). - Responsive from 360px to 1536px. Build the small screen first, then refine with `sm:` / `md:` / `lg:`. - Accessible: exactly one `<h1>`, correct heading order, real landmarks (`header`, `nav`, `main`, `footer`), text that meets WCAG AA contrast on its own background, visible focus styles, labels on every form control, and `aria-hidden="true"` on decorative SVG. - Correct in light and dark mode using Tailwind's `dark:` variants. CONTENT RULES - Write real, specific copy in the voice of a small senior consultancy. No lorem ipsum, no filler, no placeholder text of any kind. - Invent concrete details: named services, named (fictional) clients, named people with real-sounding roles. - Keep every paragraph under 45 words. REQUIRED SECTIONS, in this order 1. Sticky header: wordmark, four anchor links, one call-to-action. 2. Hero: the h1, a one-sentence subhead, two buttons, and one piece of proof (a stat row, or a client strip built from inline SVG or set type). 3. Services: four offerings, each a title plus two sentences. 4. How we work: a numbered process of four steps. 5. Case studies: three cards, each with the client, the problem, what was built, and one measurable outcome. 6. Team: four people with name, role, and one line each. 7. FAQ: five question-and-answer pairs. 8. Closing call to action with a contact form (name, email, message) that is fully labelled and needs no JavaScript. 9. Footer: nav links, a fictional Lisbon address, and a copyright line. QUALITY BAR Aim for the visual quality of a real agency site: a deliberate type scale, generous spacing, a restrained palette you actually commit to, and at least one memorable layout idea instead of nine identical stacked bands. It will be judged side by side with other studios' attempts at this same brief. Begin the file now. Output code only.
Brief v1 · fingerprint 19506ecf082b860e
A picture only shows the top of a page. Open one to get the real thing, drawn by your own browser at your own screen size.
How to read this
Start to finish is how long the app ran. File size is the page the model handed back. Neither number says the page is any good — this bench collects the pages, and judging them is a separate job we have not published yet. Open a page and decide for yourself.
How to read this
If a page opens dark, that is the model's own work: the brief asked for light and dark support, so six of the seven pages follow your device's setting.

Anthropic · run in Claude Code
What we noticed

Anthropic · run in Claude Code
What we noticed
What we saw on screen

Anthropic · run in Claude Code
What we noticed

Anthropic · run in Claude Code
What we noticed

Anthropic · run in Claude Code
What we noticed

xAI · run in Grok Build
What we noticed

OpenAI · run in Codex
What we noticed
What we saw on screen
Run 2026-08-20T05-02-20-550Z-v1 · brief v1 (19506ecf082b860e) · method v6 · test kit v6 · n = 7 · Aug 20, 2026