Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Visual verification workflow for UI changes to accelerate code review and catch ...
user-invocable
false
disable-model-invocation
true
version
1.0.0
tags
[]
progressive_disclosure
{"entry_point":{"summary":"Visual verification workflow for UI changes to accelerate code review and catch ...","when_to_use":"When working with screenshot or related functionality.","quick_start":"1. Review the core concepts below. 2. Apply patterns to your use case. 3. Follow best practices for implementation."}}
Screenshot-Based UI Verification
Visual verification workflow for UI changes to accelerate code review and catch responsive design issues early.
When to Use This Skill
Use this skill when:
Making any UI changes (components, styling, layout)
Implementing responsive design
Creating pull requests with visual changes
Want to demonstrate UI behavior without reviewers running code locally
Need to document visual state before/after bug fixes
Why Screenshot Verification Matters
Benefits
Faster Reviews: Reviewers see changes instantly without local setup
Documents Design: Creates visual record of design decisions
Visual Changelog: Historical record of UI evolution
Catches Responsive Issues: Early detection of mobile/tablet problems
Reduces Communication: Less back-and-forth about visual changes
Quality Gate: Forces conscious review of visual output
Problems It Solves
❌ "I can't reproduce the layout issue locally"
❌ "What does this look like on mobile?"
❌ "Is this the intended design?"
❌ "How does this compare to the old version?"
✅ All answered with screenshots in PR
Required Screenshots
For any PR that changes UI, capture all three viewport sizes:
1. Desktop View (1920x1080)
Full page screenshot
Key component close-ups if needed
Before and after comparisons (for fixes/refactors)
Different states (default, hover, active, error, loading)
2. Tablet View (768x1024)
Portrait orientation
Verify responsive breakpoints
Touch interaction targets visible
Menu/navigation in tablet mode
3. Mobile View (375x667)
Portrait orientation (iPhone 8/SE size - common minimum)
Touch target sizes visible (minimum 44x44px)
Scrolling behavior documented
Mobile menu states
How to Capture Screenshots
Browser DevTools Method
Chrome/Edge DevTools:
Open DevTools (F12 or Cmd+Option+I)
Toggle device toolbar (Cmd+Shift+M or Ctrl+Shift+M)
Select device preset or custom dimensions:
Desktop: 1920 x 1080
Tablet: 768 x 1024
Mobile: 375 x 667
Capture screenshot:
Full page: Cmd+Shift+P → "Capture full size screenshot"