The instructions
What every model was told
The same file and the same one-message task, for every site.
Word for word, the instruction file every model received, followed by the one-message task that pointed it at a brief. Nothing else was sent to any model: one instruction, one run, no follow-up.
Build brief (identical for every run)
You are the designer and front-end developer for a small business website. A design brief, written from a long interview with the owner, is in the JSON file named below. Read it in full: the business, audience, voice, visual direction, tensions and rules all matter.
Your job is creative: decide the design direction yourself (typography, colour, layout, rhythm, what makes this business memorable) and then build it well. Nobody will choose a direction for you and nobody will fix your pages afterwards; what you write is what is judged.
Build exactly these pages
index.html(the brief'shomepage)- the two further pages named in your task, as
<page-id>.html
Navigation may list the brief's other pages, but link only to the three pages you build; show the rest as plain text or leave them out. Every link must work.
Rules
- Plain static files: HTML plus one
styles.css. Pages must look finished with JavaScript off. A little JavaScript for enhancement is fine, never required. - Web fonts from
https://fonts.bunny.netonly (same URL shape as Google Fonts). Never link Google Fonts. - No external images and no image files. Where the design wants a photograph, draw a clearly labelled frame (for example "Photograph: Paddy at the kilns") at the size and place the design intends. Photographs will be judged as absent for everyone equally. SVG drawn in the page (marks, dividers, simple illustration) is allowed.
- Use only facts the brief states. Where it marks something to be supplied or decided, show a tasteful placeholder, never invent it.
- Must work from 390px phone width to 1440px desktop: no sideways scrolling, readable text, real contrast (WCAG AA).
- British English unless the brief's language says otherwise. No em dashes in copy.
- Do not mention AI, models, tools, or how the site was made anywhere in the pages.
Working rules
- Write ONLY inside your output folder. Do not read any other folder in the bench (other outputs exist; looking at them would spoil the test).
- When finished, reply with: the direction you chose in two or three sentences, and the list of files written. Nothing else.
Two builds per model
Each model built every site twice, from the same instruction file and the same task message, word for word. The only difference was the model's effort setting, high or medium. That is a switch on the model, not a word in the instructions, so no model was told which build it was doing.
The task message
Each run received exactly this, with the business, pages and folder filled in. The pages were the home page plus: Ardglass shop and our-story; Clydebank urban and adaptive; Otero story and visit.
Read these two files in full first: - "PROMPT.md" (your instructions, follow them exactly) - "briefs/<business>.clean.json" (the design brief) Your task: build the site for this business. Pages: index.html (home), <page>.html (the brief's `<page>` page) and <page>.html (the brief's `<page>` page), plus styles.css. Output folder (write only here): "sites/<business>-<model>/" Do not read anything else under creative-bench-c1/ besides the two files above and your own output folder. Do not run a web server. You may open your own files to check them. Keep any screenshots or temporary files inside a folder named tmp-<business>-<model> under the system temp directory, and never open a file you did not create.
Two notes, for completeness. The last sentence, about temporary files, was added after the first two Ardglass builds, to stop builds running at the same time from seeing each other's screenshots; it says nothing about design. And the instructions say photographs would be judged as absent: we then decided to add photographs to every site afterwards, the same way for all of them, so the pages look finished.