<Use_When>
- The task includes visual fidelity requirements (layout, spacing, typography, component styling)
- You have a generated screenshot and at least one reference image
- You need deterministic pass/fail guidance before continuing edits </Use_When>
<Output_Contract> Return JSON only with this exact shape:
{
"score": 0,
"verdict": "revise",
"category_match": false,
"differences": ["..."],
"suggestions": ["..."],
"reasoning": "short explanation"
}
Rules:
score: integer 0-100verdict: short status (pass,revise, orfail)category_match:truewhen the generated screenshot matches the intended UI category/styledifferences[]: concrete visual mismatches (layout, spacing, typography, colors, hierarchy)suggestions[]: actionable next edits tied to the differencesreasoning: 1-2 sentence summary
<Threshold_And_Loop>
- Target pass threshold is 90+.
- If
score < 90, continue editing and rerun/oh-my-claudecode:visual-verdictbefore any further visual review pass. - Do not treat the visual task as complete until the next screenshot clears the threshold. </Threshold_And_Loop>
<Debug_Visualization> When mismatch diagnosis is hard:
- Keep
$visual-verdictas the authoritative decision. - Use pixel-level diff tooling (pixel diff / pixelmatch overlay) as a secondary debug aid to localize hotspots.
- Convert pixel diff hotspots into concrete
differences[]andsuggestions[]updates. </Debug_Visualization>
Task: {{ARGUMENTS}}