Agent skill
visual-verification
Visually verify implemented features work correctly before marking complete. Use when testing UI changes, verifying web features, or checking user flows work in the browser.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/product/visual-verification
SKILL.md
Visual Verification
Verify implemented features work correctly through actual user interaction, not just automated tests.
When to Use
- After implementing any UI feature
- Before marking an issue as complete
- When acceptance criteria involve user-visible behavior
- After fixing UI bugs
Approaches
Web Applications: See browser-verification.md for Playwright MCP workflow.
Mobile Applications: See mobile-verification.md (Coming soon)
Verification Checklist
Before marking any UI task complete:
- Dev server is running and accessible
- Feature renders without console errors
- Elements render correctly and do not incorrectly overlap
- User interactions work as expected
- Edge cases handled (empty states, loading, errors)
- Screenshot captured as evidence
What NOT to Do
- Skip visual verification because "tests pass"
- Mark issues complete without browser testing
- Assume dev mode catches all errors (run
npm run buildtoo) - Test only happy paths
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?