- The agent matches the screenshot but guesses the wrong state or component
- Provide the route, account or fixture state, viewport, interaction sequence, and relevant component name.
- The change looks right at one width and breaks another
- Specify representative breakpoints and capture before and after evidence at each one.
- The agent hard codes styling that conflicts with the design system
- Point to existing tokens and components, and inspect the diff for one off values or duplicated patterns.
- A screenshot hides keyboard, focus, contrast, or behavior regressions
- Run the affected flow, keyboard and focus checks, automated tests, and accessibility checks in addition to comparing images.