Prompt library
The first two prompts use a {{SUBJECT}} placeholder — replace it before pasting, or let the run scripts (below) substitute it for you. Keep the subject identical across all 9; that's what makes the results comparable.
Codex — 9x wildly different website mockups
Codex CLI ($imagegen skill)
your project root
mockups/mockup-01.png … mockup-09.png + 9 named style directions
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.
agy (Antigravity) — 9x wildly different mobile mockups
agy (Google Antigravity CLI)
your project root
mockups/mockup-01.png … mockup-09.png, phone aspect, 9 named directions
Generate 9 WILDLY different mobile app UI mockups for {{SUBJECT}} using your
generate_image tool.
Rules:
- SUBJECT is constant across all 9 — same app, same home screen (listing feed,
search, one primary action). ONLY the visual style varies.
- 9 divergent directions, e.g.: iOS glass minimal, material-you expressive,
neo-brutalist, dark luxury, pastel neumorphic, retro pixel, editorial serif,
cyberpunk neon, paper-collage tactile. Name each before generating.
- One generate_image call per mockup with ImageName mockup_01 ... mockup_09.
- Phone aspect ratio (9:19-ish), single screen per image.
- After each generation, use run_command to copy the artifact into
./mockups/ as mockup-01.png ... mockup-09.png.
- If you hit an image quota error, report it immediately with the reset time
instead of retrying silently.
- Announce progress after each image.
JSON status contract — for scripting image gen at scale
any image-gen agent driven from bash
append to your generation prompt
one parseable JSON line per run — this is how inspiration-board loops over 200 styles unattended
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>"}
Converge — rebuild the winner as real code
Codex or Claude Code
project root, after picking a winner (replace 0N)
winner/index.html — real text and layout, no bitmap backgrounds
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.
Design exploration stalls on production, not taste
You sit down to design a landing page. The usual move is to build one draft and iterate. Each iteration costs an hour or more, so you see maybe three directions before you commit. That is not a taste problem — it is a production problem: you cannot prefer an option you never saw. When a mockup costs a minute instead of an hour, exploring nine directions becomes the cheap default. Prior sessions on this machine show the whole loop fitting in one sitting: one run produced five bitmap mockup directions for a storefront, collected them into a gallery page, and finished with a chosen winner rebuilt as real code.
Two CLIs, one pattern
Codex ships an $imagegen skill that routes image requests through its built-in image_gen tool — no API key required, and its contract explicitly lists UI mockups and wireframes as intended uses. The Antigravity CLI exposes a generate_image tool the same way. Both run non-interactively (codex exec "…" / agy -p "…") and both follow the same batch rule: one image call per mockup, never a switch to an API fallback.
Two traps, both from real runs. Codex saves built-in image output under $CODEX_HOME/generated_images/ — if your prompt doesn't say "copy each image into ./mockups/", the run can succeed while your project folder stays empty. And agy's --print-timeout defaults to five minutes; nine images take longer, so the run script raises it to fifteen. The failure signal for both is the same: an empty contact sheet. Read the run log before blaming the model.
Hold the subject constant
Nine images are only useful if you can compare them, and they are only comparable if exactly one variable changes. "Make nine cool designs" gives you nine incomparable posters. "Same homepage, same hero, same call to action — nine styles" gives you a controlled experiment you can read at a glance. The inspiration-board pipeline enforces this discipline with a shared subject file appended to every style prompt, "so you can compare how each visual approach handles" the same material. Before you run, write your subject as one sentence that names the page type and its content; if a mockup comes back as a different page type, regenerate it — don't compare it.
From party trick to 200-style pipeline
Nine mockups is a live demo. Two hundred is a pipeline, and the difference is error handling. The inspiration-board project generates its images by driving the Antigravity CLI from a bash loop across 200 named web-design styles. Its generator demands machine-readable status from every run — the JSON contract in the prompt library above — fixes each output filename in advance, and skips any file already on disk above 100 KB, so quota-interrupted runs resume instead of restarting. When your own loop grows past a handful of images, adopt those in order: fixed names, skip-if-exists, JSON status, then background jobs with progress lines.
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 — masonry grid, infinite scroll, carousel, lightbox, compare-split, magazine editorial, filmstrip, table list, mood board, fullscreen slideshow, grouped categories, search-first.
Bitmap to real code
The mockups are bitmaps — for deciding, not shipping. The loop closes when you pick one tile and hand it back to a coding agent as a reference image, using the converge prompt in the library. Your decision rule: pick the tile you would be embarrassed to lose. If no tile clears that bar, the styles were not divergent enough — widen the directions and rerun rather than polishing the least-bad option.