Build a complete page without ceremony, use focused checks for uncertainty, understand quick versus full review, and report evidence rather than treating missing checks as passes.
Where: Designer assistant → design_workflow for optional progress; review_page for rendered QA.
Key ideas
- The ledger is optional, not a serial gate: The host tracks structure, content, visual, responsive, basic interactions, advanced motion, controls, and final evidence. design_workflow status/start/check can show progress or scope a concern, but authoring does not require starting and checking every phase in sequence.
- Quick review is free measurement; full review is visual judgment: review_page depth quick (the default) renders desktop and phone and measures layout, readability, overflow, placeholders, and direction evidence without a vision-model round. depth full captures both widths (or deck slides) and asks for a visual verdict; reserve it until quick checks are clean.
- Coverage is explicit: focus/focuses can request structure, content, visual, responsive, basic-interactions, advanced-motion, and controls facets together. element_ids narrows a check to existing roots; results report which requested targets were checked and whether evidence is verified, failed, partial, unsupported, or unavailable.
Steps
- Build a complete usable page in cohesive batches; no phase-start ritual is required.
- Use design_workflow status if you need the current ledger, start only when intentionally scoping a layer, and check only when a focused concern needs evidence.
- For routine iteration, call review_page with depth quick. Supply checks for important requirements and focuses for the QA facets that matter.
- Resolve failed and partial evidence, then run one depth full visual review after the quick pass is clean. Full review is the paid visual look, not a substitute for interaction playback or source verification.
- Repair concrete findings in a batch. If the evidence says unsupported or unavailable, state that limitation instead of calling it a pass.
- At handoff, report the verified facets, failed/partial items, and anything that still needs a real-device, playback, or public-link check.
Seven scoped QA facets
- Structure — hierarchy and requested page pieces.
- Content — copy and brief coverage.
- Visual — rendered composition and legibility.
- Responsive — desktop/phone behavior.
- Basic interactions — supported click/hover/control behavior.
- Advanced motion — timed and scroll-driven behavior.
- Controls — exposed fields and requested editable controls.
review_page inputs
- depth: quick or full; quick is the default.
- focus: one facet, or focuses: several facets in one render.
- element_ids: up to the declared limit of existing element roots; coverage is returned explicitly.
- checks: extra acceptance conditions such as connected design system or full-bleed hero.
- auto_fix: optional deterministic contrast repair; defaults off so review-only does not modify the page.
Optional workflow ledger
- status reads the current build ledger.
- start scopes a phase and may record element_ids.
- check runs targeted QA; normal completion checks applicable facets together.
- The final host gate runs whole-page regressions and may reserve one full visual review.
Tips
- Batch independent reads and known-target edits, but keep writes and playback checks ordered.
- Use a focused check to settle a real uncertainty; do not call one phase at a time just to advance the ledger.
- A screenshot proves appearance at one captured state, not playback, backward scrubbing, accessibility, or external data accuracy.
Limitations and important notes
- Quick is measurement, not a vision-model opinion; full is the visual review.
- A facet may be partial, unsupported, or unavailable. Those states are not passes.
- The workflow ledger is optional for authoring and should not be presented as a required onboarding ceremony.
Troubleshooting
The review did not inspect the requested layer.
Check the returned coverage for the exact element id and facet. Use a valid existing id and rerun the relevant scoped check.
I want a visual opinion but only got measurements.
After quick findings are clean, request review_page with depth full; this is the visual pass and consumes the reserved review.