visual-verdict
SolidStructured visual QA verdict for screenshot-to-reference comparisons
Install
Quality Score: 95/100
Skill Content
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
visual-verdict
Structured visual QA verdict for screenshot-to-reference comparisons
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.
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.
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.
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.