visual-verdict

Solid

Structured visual QA verdict for screenshot-to-reference comparisons

AI & Automation 35,484 stars 3242 forks Updated today MIT

Install

View on GitHub

Quality Score: 95/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

<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 `/oh-my-claudecode:visual-verdict` before any further visual review pass. - Do **not** treat the visual task as complete until the next screenshot clears ...

Details

Author
Yeachan-Heo
Repository
Yeachan-Heo/oh-my-claudecode
Created
4 months ago
Last Updated
today
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

visual-verdict

Structured visual QA verdict for screenshot-to-reference comparisons

1 Updated today
ItsProGamer974
AI & Automation Solid

visual-verdict

Screenshot comparison QA for frontend development. Takes a screenshot of the current implementation, scores it across multiple visual dimensions, and returns a structured PASS/REVISE/FAIL verdict with concrete fixes. Use when implementing UI from a design reference or verifying visual correctness.

496 Updated 1 months ago
vibeeval
Web & Frontend Listed

screenshot-feedback

Use after capturing a screenshot during a feedback loop, to audit whether the rendered output matches a reference image, or the project's design criteria. This skill triggers on a request for screenshot comparison, attempts to audit rendered output, statements stating that the rendered output did match descriptions or reference, or any invocation passing a screenshot path. Outputs a verdict, grouped P1/P2/P3 findings tied to likely source locations, and a recommended next action. Skips for static code review or pre-render design work.

0 Updated today
Kevinnnnn-ai
Testing & QA Listed

visual-qa

Visual quality assurance: analyze game screenshots for defects, compare against reference, check motion in frame sequences. Supports runtime-native inspection plus Gemini or OpenAI API-backed VQA.

2 Updated yesterday
RandallLiuXin
Web & Frontend Listed

visual-review

Visually verify rendered output for web pages, PRs, CLI commands, and TUIs. Use when the user asks for "visual review", "visual QA", "screenshot this", "check how this PR looks", "review CLI output", "capture a terminal command", or "record this TUI". Inputs - target URL or PR number, mode (browser / CLI / TUI / regression), and routes / commands / viewports to check. Do not use when the user wants functional QA (use a testing skill), brand-taste judgment (this verifies rendered output, not design taste), frontend-stack migration (out of scope), or wants to push commits (this is read-only). Produces a screenshot or recording set + a visible-issues report listing artifact paths, routes/commands/viewports inspected, and any layout/overflow/state-coverage gaps found. Escalate if the target is unreachable, the PR is too large for a single review pass (recommend scope reduction), or the local dev server cannot start.

1 Updated today
Naoray