visual-verdictlisted

<Purpose> Use this skill to compare generated UI screenshots against one or more reference images and return a strict JSON verdict that can drive the next edit iteration. </Purpose> <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> <Inputs> - `reference_images[]` (one or more image paths) - `generated_screenshot` (current output image) - Optional: `category_hint` (e.g., `hackernews`, `sns-feed`, `dashboard`) </Inputs> <Output_Contract> Return **JSON only** with this exact shape: ```json { "score": 0, "verdict": "revise", "category_match": false, "differences": ["..."], "suggestions": ["..."], "reasoning": "short explanation" } ``` Rules: - `score`: integer 0-100 - `verdict`: short status (`pass`, `revise`, or `fail`) - `category_match`: `true` when the generated screenshot matches the intended UI category/style - `differences[]`: concrete visual mismatches (layout, spacing, typography, colors, hierarchy) - `suggestions[]`: actionable next edits tied to the differences - `reasoning`: 1-2 sentence summary <Threshold_And_Loop> - Target pass threshold is **90+**. - If `score < 90`, continue editing and rerun `$visual-verdict` before any further code edits in the next iteration. - Persist the verdict in `.omx/state/{scope}/ralph-progress.json` with both: - nu