# Generated UI Review Workflow

Use this after an agent or human has drafted UI.

## Review Steps

1. Identify the intended user job, platform, consequence severity, reversibility, and interruption cost.
2. Name the pattern the UI appears to use. If no pattern is explicit, infer the nearest pattern from the compact index.
3. Load the selected pattern contract and any nearby comparison pack.
4. Check whether the UI includes every required state from the pattern contract.
5. Check keyboard behavior, accessibility notes, recovery paths, and focus/return behavior.
6. Apply the anti-pattern checklist.
7. Return findings as concrete revisions, not generic UX advice.

## Finding Format

- Pattern: selected pattern and why it fits.
- Alternatives rejected: nearby patterns and why they do not fit.
- Missing states: required states absent from the UI.
- Contract breaks: interaction or keyboard requirements that are violated.
- Anti-pattern risks: named anti-patterns that appear.
- Required revision: concrete UI changes.