Inspect rendered browser screenshots for visual defects in layout, typography, contrast, and spacing.
npx skills add https://github.com/izzoa/polyrouter --skill ss-verify
Please help me install this Agent Skill. Skill: ss-verify Source: https://github.com/izzoa/polyrouter/tree/main/.agents/skills/ss-verify Command: npx skills add https://github.com/izzoa/polyrouter --skill ss-verify
This Skill catches visual issues that code review misses, like awkward spacing, unreadable text, broken font loading, weak contrast, and screens that look fine in source but bad in pixels.
Render the target screen in a browser, inspect the screenshot visually, and repeat after any fixes until the page looks balanced, readable, and polished.
High-intent search queries and answers about installing and using this skill.
To catch visual UI defects missed by code review, inspect browser-rendered screenshots to verify layout, typography, contrast, and spacing. This perceptual checking identifies awkward spacing, broken font loading, and weak contrast that source code analysis cannot detect.
Verifying empty, loading, and error states in a web UI requires rendering each state in a browser and inspecting the captured screenshot. This visual review confirms that missing UI elements or broken layouts do not slip through during isolated component development.
Inspecting browser rendering for layout inspection involves opening a route, static page, or isolated component in a browser, capturing a screenshot, and performing a perceptual check of the actual pixels to judge visual quality and balance.
Yes, visual verification works for static pages and isolated components by rendering the target screen in a browser and inspecting the resulting screenshot. It applies perceptual checks across happy, empty, loading, and error states to ensure readability.
A dashboard page passing code checks but looking unbalanced on desktop indicates visual flaws like awkward spacing or weak contrast. You must render the screen, inspect the screenshot visually, and iterate on fixes until the page looks balanced and polished.
To fix typography and contrast issues found during screenshot review, adjust the source code, re-render the target screen in the browser, and capture a new screenshot. Iterate this process until the visual output looks readable and correct.
ShmurdocAutomate headless Chromium browser control for QA testing and site verification.
dropsyoonCompares UI screenshots against reference images and outputs a JSON verdict with differences and edit suggestions.
algusaemCodify loading, error, and empty state patterns for React components.
bejranondaDetect JavaScript errors and collect browser diagnostics from web pages.
