Agentic Software Factory · 2026-07-17 · Socratic Dialogue
“Why not just build nine real pages?”
The variations section as the workshop room actually runs it: skeptical questions drive the reveal, and each answer lands the real prompt or command exactly where the question demands it.
The room asks
It can — at roughly an hour a draft, which is why you normally see three directions before you commit. A bitmap mockup costs about a minute, so nine directions becomes the cheap default, and you can't prefer an option you never saw. Images are for deciding; code is for shipping. Generate to diverge, code to converge. Here's the whole first taste, one paste — fair warning: it launches Codex, a paid agent, with sandboxing and approvals off, so read it and be comfortable with the cost and permissions before you run it:
mkdir -p mockups
codex exec --dangerously-bypass-approvals-and-sandbox 'Use the $imagegen skill to generate 9 WILDLY different website homepage mockups for a landing page for an indie coffee roaster. The subject stays identical in all 9 - ONLY the visual style varies. One built-in image_gen call per mockup. After each image completes, copy it from $CODEX_HOME/generated_images/ into ./mockups/ as mockup-01.png ... mockup-09.png. Announce progress after each one.'
ls mockups/
Only if you let the subject drift. The prompt pins the subject — same product, same page type, same rough content — and varies nothing but the style. That turns nine images into a controlled experiment you can read at a glance. This is the exact prompt, verbatim (the agy mobile version is on the guide):
Use the $imagegen skill to generate 9 WILDLY different website homepage mockups
for {{SUBJECT}}.
Rules:
- The SUBJECT stays identical in all 9 — same product, same page type
(homepage), same rough content (hero, nav, one CTA). ONLY the visual style
varies. This is what makes them comparable.
- Pick 9 maximally divergent directions, e.g.: swiss/international typographic,
neo-brutalist, glassmorphic dark, editorial magazine, retro terminal,
playful memphis, luxury minimal, bento-grid dashboard, hand-drawn zine.
Name each direction before generating.
- One built-in image_gen call per mockup (do NOT drop to the CLI fallback).
- Desktop aspect, full homepage visible, legible headline text.
- After each image completes, copy it from $CODEX_HOME/generated_images/
into ./mockups/ as mockup-01.png ... mockup-09.png (match the direction
order you announced).
- Announce progress after each one — never go silent.
- When all 9 exist, list the 9 directions next to their filenames.
And if one mockup comes back as a different page type anyway: regenerate it. Don't compare it.
mockups/ folder is empty. So the model lied?No — it saved your images, just not where you looked. Codex's built-in image_gen writes to $CODEX_HOME/generated_images/ by default, which is why the prompt explicitly orders a copy into ./mockups/. The other classic: agy's --print-timeout defaults to five minutes, and nine images take longer — the run script raises it to fifteen. An empty contact sheet means read the run log before blaming the model.
Open the contact-sheet gallery — it polls every five seconds, so tiles fill in live while the run generates — and pick the tile you would be embarrassed to lose. If nothing clears that bar, your styles weren't divergent enough: widen the directions and rerun. Never polish the least-bad option.
You hand the winner back to a coding agent as a reference image. The bitmap decided; the code converges:
mockup-0N.png is the winner. Rebuild it as a real single-file HTML/CSS page at
./winner/index.html, using the image strictly as a visual reference — real
text, real layout, no bitmap backgrounds.
Real text, real layout, no bitmap backgrounds — the image is strictly a visual reference.
That's exactly what inspiration-board is: a bash loop driving the Antigravity CLI across 200 named web-design styles. Scale is mostly error handling — fixed output filenames, a skip-if-exists guard (file already on disk above 100 KB), and machine-readable status demanded from every single run:
Respond with ONLY a JSON object (no markdown, no explanation):
- Success: {"status":"ok","path":"<output_path>"}
- Quota error: {"status":"quota_exhausted","reset_seconds":<N>,"reset_time":"<ISO8601>"}
- Other error: {"status":"error","message":"<description>"}
Quota errors are real; a JSON reset time beats a silent retry. And the variations idea applies twice there: the images are style variations, and the gallery pages themselves are twelve layout variations of the same image set.
The page you're reading is the proof. Its theme was picked by this exact loop: wildly different theme candidates rendered over this section's real content, three rounds of Elo voting, 130 recorded votes — and the winner, Instrument Panel, undefeated in both light and dark, became the template for every site in this workshop. The annotated transcript is on the Session Replay page.
And you can take the winner home: the resulting here-now-workshop-page skill is downloadable and installable from the guide.