screenshot-validation
FeaturedValidate screenshot and viewer HTML quality for PR evidence. Run this after adding or modifying images under .agents/evidence/pr/ or .agents/recordings/, or after generating a new viewer HTML file. Combines image quality checks (resolution, blankness, file size) with Playwright-based viewer rendering verification.
Install
Quality Score: 96/100
Skill Content
Details
- Author
- liaohch3
- Repository
- liaohch3/claude-tap
- Created
- 7 months ago
- Last Updated
- 4 days ago
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
visual-verification
Automated visual regression check via Playwright — 5 DOM checks × 3 viewports (375/768/1280). Produces pass/fail grid + screenshot paths under .arbiter/evidence/visual/.
visual-validate
Validate UI changes in a real browser via Chrome DevTools or Playwright MCP — before/after screenshots, console and network capture. Use when asked to "visual validate", "check the UI", "screenshot before/after", or after a UI change. Don't use for unit tests (/tdd), E2E flows (/e2e), or backend changes.
verify
Visually verify UI changes by taking authenticated screenshots of the local dev server, with a measurement sweep for what shouldn't be eyeballed. Use after editing any view, template, component, or layout file. For non-trivial UI work spanning several screens, breakpoints, or states, use vischeck:review instead. If screenshot redirects to a login page, invoke vischeck:setup-auth first.