---
schema_version: 1
revision: "22ce5d34dbcb5a78"
id: "codex-visual-review"
title: "Review generated UI before building"
---

# Review generated UI before building

A generated mockup is useful when it gives you **something concrete to inspect**. Do not jump from one polished image to implementation. Keep the source visual, choose a controlled style direction, generate against that direction, review the result, then hand the chosen direction to a build pass with explicit constraints.

## Start From A Real Visual

Use an existing screenshot, mockup, or product frame as the anchor. The agent should know **what it is changing** instead of inventing the whole interface from scratch.

For product work, this could be a checkout screen, a settings panel, a saved listings card, or a dashboard slice. The point is to **keep the job of the screen stable** while the visual direction changes.

## Name The Style Before Generating

Ask for a **numbered list of style directions** first. Then refer to the style by number in the next prompt. That gives the agent a stable design target instead of asking it to invent the language at the same time it generates the mockup.

> As long as you have that list ahead of time. So that, just in time, it doesn't have to come up with new ideas. You'll have much better results.
>
> — John Lindquist

## Generate Against One Direction

Use the **selected style as the variable**. Keep the screen purpose, product type, data model, and interaction intent stable.

If the source is a saved listings mobile screen, the generated version should still help someone scan saved listings. The typography, surface treatment, spacing rhythm, or color system can change. The task should not quietly become a different product.

## Review The Image As Evidence

Treat the generated image as **review material, not finished UI**. Check what changed, what survived, what broke, and whether the result is still reasonable to build.

Review against:

- Did the screen keep the same job?
- Did the primary action stay obvious?
- Did the content survive the style change?
- Is the spacing intentional or just empty?
- Would this be reasonable to implement?
- What should the build pass preserve?
- What should the build pass reject?

## Hand Off To A Build Pass

The next step is not more wandering. Tell the agent **what won, why it won, what to preserve, what to fix, and what proof counts**.

```text
Use the selected generated mockup as the visual reference.

Build a real implementation of this direction.

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

Fix:
- unreadable text
- impractical spacing
- missing accessibility states
- inconsistent component behavior

Verification:
- run the project checks
- capture desktop and mobile screenshots
- compare the result against the selected mockup
- list any visual mismatches that remain

Do not restart the visual exploration.
```

## Copyable Prompt: Controlled Visual Variation

```text
Use the provided UI screenshot as the source visual.

Goal:
Create a new visual direction for the same mobile screen.

Style direction:
Use style 6 from the saved style list.

Keep unchanged:
- screen purpose
- information hierarchy
- primary user action
- core data shown on the card
- mobile-first layout

Change only:
- visual style
- spacing rhythm
- typography feel
- surface treatment

Return:
- one generated mockup
- a short review of what changed
- what must be preserved in a real implementation
```

## Branch Useful Context

When a design conversation starts working, **name it and fork it** before trying a risky direction. A fork is a saved branch of useful context. Use it for experiments you may abandon. Do not depend on throwaway side chats for work you might need later.

> A side chat in an ephemeral fork. I'm not a fan of those. I don't like ephemeral things with agents. I never want to lose anything.
>
> — John Lindquist

## Carry Forward: Workspace Layouts

This workflow creates repeated surfaces: source visuals, style lists, generated variants, review notes, implementation passes, and screenshots. Workspace layout matters once the build pass begins: keep the accepted visual direction, implementation files, and verification screenshots easy to compare.

## Related resources

- [Companion reference](https://lapis-fossil-vsbc.here.now/#visual-review)
- [Resource directory and portable download](/topics/codex-resources/)
- [Published recording](https://www.dropbox.com/scl/fi/3m5p2dwkx0imuyu0dq5os/GMT20260626-155513_Recording_gallery_1920x1080.mp4?rlkey=60j5649let6pt4fdxpggozv1q&st=qhbuo513&dl=0)

## Original references

- [Codex workflows companion](https://lapis-fossil-vsbc.here.now/#visual-review)
- [Published workshop recording](https://www.dropbox.com/scl/fi/3m5p2dwkx0imuyu0dq5os/GMT20260626-155513_Recording_gallery_1920x1080.mp4?rlkey=60j5649let6pt4fdxpggozv1q&st=qhbuo513&dl=0)
