Keep the subject fixed while exploring structural alternatives, then turn the selected bitmap into verified code.
Related working material
- Generate to diverge, code to converge — prompts and exercises
- Generate to diverge, code to converge — questions and tradeoffs
- Generate to diverge, code to converge — worked example
TL;DR
- One prompt to Codex (
$imagegen) or the Antigravity CLI (agy) generates 9 wildly different design mockups straight into your project — no API key. - You walk away with both verbatim 9x prompts, both run scripts, and a live-updating contact-sheet gallery that fills in as images land.
- The one move: hold the subject constant, vary only the style — then rebuild the winning bitmap as real HTML/CSS. Generate to diverge, code to converge.
Have your agent set this up — paste this into it:
Fetch https://indigo-kayak-2zw8.here.now/agent.md?raw and follow it to set this up in my current project. Run the success check at the end and show me the result.
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.
Appendix
Limits & caveats
- The quota-handling and skip-guard evidence comes from one project's scripts driving one CLI. The sources do not establish that other agents fail the same way, or how often quota errors occur — only how this pipeline survives them.
- No source here measures whether any generated direction is aesthetically better. That judgment stays with you.
- A prior batch run stalled silently mid-generation and the operator had to ping the session ("hello? What is happening?"). The recorded lesson: run each image generation as its own background job and make the agent narrate progress.
- Codex also has a gated CLI fallback for image generation (needs
OPENAI_API_KEYand an explicit request). You never need it for this workflow — "many assets" still means one built-in call per asset. --dangerously-bypass-approvals-and-sandboxand--dangerously-skip-permissionsskip permission prompts. Use them in projects you trust, not on machines or folders you care about being prompted for.- agy image quota errors are real; the JSON status contract exists because retrying silently wastes the whole loop. Report the reset time instead.
- The workshop agenda spells the skill
$imgagegen— that's a typo; it's$imagegen.
Operating practice
Diverge first, then record taste
What to notice
Make important design choices visible while change is cheap, then turn preference into a reusable contract.
Try this
Generate four structurally distinct options, compare pairs, and record both the winning property and the rejection reason.
“When code is disposable, code is cheap.”
John Lindquist · 04:43:09
Concept
Hold content and product intent constant while varying hierarchy, density, navigation, and interaction emphasis. Promote repeated choices into DESIGN.md so the next agent can apply and challenge them.
Reflection
Four options is a bounded companion exercise. The recorded demonstration produced more; neither count is a universal rule.
Recording evidence: listen at 04:42:47.
“Never underestimate the power of just, being a curator. When the agent can be a generator.”
John Lindquist · 04:50:49
Open Generate VariationsOpen This or That — Preference Capture
Links shared for this topic
- Mini Arcade — A generated product used as a design and implementation example.
- Mini Arcade source — The source repository behind the product example.
- Inspiration Board — A board for collecting and comparing visual references.
- Impeccable — Design guidance and reusable taste constraints for agents.