Have Designer look at the rendered page, interpret its ten-part scorecard, apply bounded patches, and stop after the permitted review rounds.
Where: Designer assistant after building or materially restyling a page → review_page.
Key ideas
- A rendered review, not a code lint: review_page renders desktop screenshots of the top, middle, and bottom, or every slide in a deck, then asks a vision reviewer to judge what is actually visible. Static markup checks cannot detect a page made from repetitive centered sections, weak imagery, or accidental empty space.
- Ten scored dimensions: The reviewer scores hierarchy, typography, color, spacing, imagery, layout variety, overlap/header behavior, empty space, art-direction conformance, and brand specificity from 1 to 5. A score of 2 or lower, or three scores of 3, produces a fix verdict. Direction must be at least 4 to ship.
- Bounded, patch-only correction: Each review returns no more than six concrete fixes. Apply those to named elements or selectors without replacing a working page wholesale. Two rounds are the normal maximum; a third is allowed only when the direction score rose between rounds but remains below 4.
Steps
- Finish the first coherent build or restyle before reviewing; do not spend a vision round on an empty scaffold.
- Call review_page with the page id when needed, the user’s brief, and any non-negotiable checks such as a full-bleed hero or connected design system.
- Read the verdict and every 1–5 score. Prioritize the returned fixes in order because they are capped at six by impact.
- Patch the identified element or rule. Preserve correct content, IDs, and interaction wiring; do not shrink the whole page to make a fit check pass.
- Review once more after the corrections. Stop when the verdict is ship or when the round budget is exhausted.
- If a weakness remains at the limit, tell the user plainly what is still weak and what a larger redesign would require.
What “ship” means
- No score may be 2 or lower.
- Three or more scores of 3 force a fix verdict.
- Art-direction conformance below 4 always forces a fix verdict even if the overall page looks polished.
- A ship verdict returns no fixes; a fix verdict returns at most six, each with a concrete target and action.
Round accounting
- A review with an unreadable response still counts and ends the loop rather than silently buying another try.
- The normal limit is two reviews per page per Designer session.
- A third review is allowed only for measurable direction convergence: round two’s direction score is higher than round one’s and still below 4.
- Reloading begins a new session; it is not a reason to deliberately evade the budget.
Current write and review guardrails
Designer now preserves useful partial work while refusing destructive corruption. A non-user transaction that empties a page is reversed and named; invalid exposed fields or interactions are dropped while valid siblings still write; stylesheet parse faults fail, while unsafe system-token/kit declarations are removed and the remainder is applied.
- Primitive controls receive design-system classes during writes and a post-write sweep.
- Contrast is measured per element and, for text over imagery, against sampled raster tiles.
- Deck review checks each slide’s final frame so hidden or exited copy is not mistaken for visible content.
- Reviews stay grounded in the user brief, exact slots, current direction, system knobs, sticky overlays, gallery travel, and pinned/scrub runtime behavior.
- Targeted edits preserve authored motion and transforms outside the requested scope.
Tips
- Include the actual audience, brand, and desired feeling in the brief. The reviewer cannot judge brand specificity from “make it nice.”
- Fix composition before polish: hierarchy and layout variety usually matter more than a tiny shadow or border adjustment.
Limitations and important notes
- The review uses desktop rendering; still test responsive breakpoints and actual interaction behavior separately.
- The reviewer can identify likely visual problems but cannot prove accessibility, content accuracy, or provider-side media rights.
- A successful screenshot does not validate video playback, CMS data, or an exported archive.
Troubleshooting
The page gets a low direction score despite looking polished.
Polish is not conformance. Compare the type, grid, color proportions, imagery, and never-rules to the selected direction specimen.
A third review is refused.
Apply the last fixes and stop. A third round is reserved only for an improving direction score that is still below the ship floor.