Generate controlled, verified variations

When code and design candidates are cheap, the mistake is not generating too many. The mistake is generating them randomly. Start by defining the candidates, keep the comparison controlled, run each option through the same constraints, and review the…

When code and design candidates are cheap, the mistake is not generating too many. The mistake is generating them randomly. Start by defining the candidates, keep the comparison controlled, run each option through the same constraints, and review the outputs on a surface that makes the decision obvious enough to defend later.

Start With A Candidate List

Ask the agent to generate the dataset first: styles, strategies, prompts, layouts, implementation approaches, or test boundaries. Remove duplicates, rename vague entries, and make sure each candidate is different for a reason.

To do variations, like, you come up with the variations first.

— John Lindquist

Vary One Thing At A Time

If every candidate changes layout, data model, tests, and copy, you are no longer comparing candidates. You are just admiring chaos with a folder structure.

Use The Same Base Prompt

Candidate prompts should differ only by the named variable. Keep the base prompt, constraints, review criteria, and verification command identical.

Fan Out After The Matrix Is Clear

Parallelization is useful after you know what each lane is supposed to test. Treat the candidate list like data: each lane gets a candidate id, one variable setting, and the same proof requirement.

I definitely wouldn't rely on setting a long loop… Because then you get into, like, after a while, compaction and other things where you lose that context and things start to look alike.

— John Lindquist

Preserve The Review Surface

For UI work, use screenshots or a gallery. For code, use diffs, test logs, and a short comparison table. Save the artifacts before choosing so the decision does not disappear into memory.

Pick, Combine, Refine, Expand, Or Reject

Those are the valid outcomes. Choose one explicitly. If two candidates each have one strong idea, combine the named pieces. If the whole batch is wrong, reject the batch and update the matrix.

Turn The Winner Into A Real Build

A generated mockup is direction, not shipped UI. Use the selected candidate as the reference for a verified implementation pass. The next prompt should say what won, why it won, what to preserve, what to fix, and what proof counts as done.

Copyable Prompt: Candidate Matrix

Create a variation matrix for a software UI concept.

Goal:
Design a mobile app screen for browsing saved listings.

Variable under test:
Visual layout direction.

Generate 8 candidate directions.

For each candidate, include:
- id
- layout direction
- design constraints
- what should stay identical
- what would make this candidate fail review

Do not generate the UI yet.
Return the candidate matrix first.

Copyable Prompt: Refine The Winner

Continue from this saved variation decision.

Outcome:
Refine.

Primary candidate:
v2.

Why:
It best preserves the constraints and passes the review criteria.

Preserve:
- the selected layout structure
- the interaction model
- the accepted visual hierarchy

Fix:
- tighten spacing on mobile
- improve empty-state copy
- keep the same data model

Verification:
Run the same verification command from the matrix and save the result.

Do not reopen the candidate search.

Source references