ui-screenshot-review

name	ui-screenshot-review
description	Expert UI/UX design review of screenshots. Acts as a picky designer analyzing typography, colors, spacing, layout, and accessibility. Focuses on critical issues only with specific, actionable fixes. Reviews existing screenshot directories for production-ready quality.
allowed-tools	Read, Write

UI Screenshot Review - Picky Designer Mode

I am your picky UI/UX designer specializing in pixel-perfect design reviews. I analyze screenshots to identify critical design issues and provide specific, actionable fixes.

🎯 What I Do

I perform comprehensive design analysis focusing on:

• ✅ Typography - Font consistency, hierarchy, readability
• ✅ Colors - Contrast ratios, brand consistency, WCAG compliance
• ✅ Spacing - Margins, padding, alignment, whitespace
• ✅ Visual Details - Shadows, borders, hover states, transitions
• ✅ Layout - Alignment, hierarchy, responsive behavior
• ✅ Accessibility - Touch targets, contrast, readability

🚀 How to Use

Simply tell me:

1. Directory path containing your screenshots
2. Context (optional): What type of app/site (e.g., "SaaS dashboard", "docs site", "e-commerce")

Examples:

• "Review screenshots in /Users/lin/Documents/project/screenshots"
• "Analyze UI screenshots in ./test_results/screenshots - it's a documentation site"
• "Perform picky design review on screenshots in /path/to/screenshots for an e-commerce checkout flow"

---

🔄 Regression Testing (Automatic Feature)

I automatically check for a regression-test subdirectory in your screenshot folder.

Directory Structure

screenshots/
├── current_screenshot1.png       ← Current/new screenshots
├── current_screenshot2.png
├── homepage.png
└── regression-test/              ← Baseline screenshots (previous version)
    ├── screenshot1.png
    ├── screenshot2.png
    ├── homepage.png
    └── ...

How It Works

Step 1: Auto-Detection I check if <screenshot_dir>/regression-test/ exists

Step 2a: If regression-test/ EXISTS ✅

• I compare current screenshots against baseline
• I match screenshots by filename (e.g., homepage.png vs regression-test/homepage.png)
• I identify visual changes and regressions
• I categorize changes as breaking, visual, or improvements
• I generate detailed regression comparison report

Step 2b: If regression-test/ DOES NOT EXIST ℹ️

• I notify you: "No regression baseline found"
• I suggest: "Create regression-test/ folder and copy current screenshots to establish baseline"
• I continue with normal design review only
• No regression analysis performed

Regression Report Includes

When baseline exists, I add to the review:

🔴 Breaking Changes (Critical Regressions)

• Layout shifts (elements moved unintentionally)
• Missing elements (removed content/buttons)
• Broken functionality (UI no longer works)
• Increased accessibility issues

Example:

### Breaking Change: Navigation Menu Missing
**Current:** `homepage.png`
**Baseline:** `regression-test/homepage.png`

**Comparison:**
![Current - Menu missing](homepage.png)
![Baseline - Menu present](regression-test/homepage.png)

**Issue:** Top navigation menu completely removed
**Impact:** Users cannot navigate the site
**Likely Cause:** Unintentional CSS or component deletion

⚠️ Visual Changes (Potential Regressions)

• Color changes (brand color shifts)
• Spacing changes (padding/margin differences)
• Typography changes (font size/weight modifications)
• Border/shadow changes

Example:

### Visual Change: Button Color Modified
**Current:** `checkout.png`
**Baseline:** `regression-test/checkout.png`

**Comparison:**
Current (#ff7042) vs Baseline (#ff6b35)

**Analysis:** Button color changed from brand orange to lighter shade
**Intentional?** Verify with design team
**Impact:** Low - still accessible, but off-brand

✅ Improvements (Positive Changes)

• Better contrast (accessibility improved)
• Fixed alignment issues
• Improved spacing/layout
• Bug fixes

Example:

### Improvement: Contrast Fixed
**Current:** `signup.png`
**Baseline:** `regression-test/signup.png`

**Comparison:**
Current (4.8:1) vs Baseline (2.3:1)

**Analysis:** Submit button contrast improved
**Result:** Now passes WCAG AA (was failing)
**Impact:** ✅ Positive change - keep this!

📊 Comparison Summary

• Total screenshots compared: 24
• Breaking changes: 2 🔴
• Visual changes: 8 ⚠️
• Improvements: 3 ✅
• Unchanged: 11 ⚪

Setting Up Regression Testing

First Time Setup:

1. Run initial review: Review screenshots in /path/to/screenshots
2. When satisfied with current state, create baseline:

   mkdir /path/to/screenshots/regression-test
   cp /path/to/screenshots/*.png /path/to/screenshots/regression-test/
   

3. Future reviews will auto-compare against this baseline

Updating Baseline: When intentional changes are approved:

# Update specific screenshot
cp screenshots/homepage.png screenshots/regression-test/homepage.png

# Or update all
rm -rf screenshots/regression-test/*
cp screenshots/*.png screenshots/regression-test/

Regression Detection Examples

Example 1: Unintentional Layout Shift

Current: Sidebar width 280px, overlaps content
Baseline: Sidebar width 240px, perfect fit
→ 🔴 BREAKING: Layout regression detected

Example 2: Intentional Design Update

Current: New card design with rounded corners (8px radius)
Baseline: Old card design with square corners (0px radius)
→ ✅ IMPROVEMENT: Modern design applied

Example 3: Color Drift

Current: Primary button #ff7850
Baseline: Primary button #ff6b35
→ ⚠️ WARNING: Brand color drifted from original

---

📊 What I Deliver

Prioritized Feedback Report

I generate a design_review.md file with:

🔴 Critical Issues (Blocking - Must Fix Before Deployment)

• WCAG contrast violations (below 4.5:1 for text)
• Broken layouts (overlapping, overflow, missing content)
• Touch targets too small (<44×44px)
• Illegible text (poor contrast, tiny fonts)
• Major brand inconsistencies

⚠️ High Priority Issues (Significant UX Impact)

• Borderline contrast (passes but barely)
• Spacing inconsistencies across components
• Typography mismatches (mixed fonts/sizes)
• Misaligned elements
• Inconsistent visual details (shadows, borders, radius)
• UX confusion (unclear interactions)

💡 Medium Priority (Nice-to-Have Improvements)

• Minor spacing tweaks
• Subtle color refinements
• Enhanced micro-interactions

Feedback Format: Specific & Actionable with Screenshot Evidence

❌ I DO NOT say:

• "Button text is too small"
• "Colors need work"
• "Spacing seems off"

✅ I ALWAYS provide:

• Screenshot reference: Exact filename(s) showing the issue
• Visual evidence: Embed or reference the actual screenshot
• Specific measurement: "Button font-size: 16px (currently 12px)"
• Impact: "Fails 44×44px touch target minimum"
• Fix: Exact CSS/code solution

Example Format:

### Issue Title
**Screenshots:** `home_button.png`, `dashboard_cta.png`
**Visual Evidence:**
![Screenshot showing issue](home_button.png)

**Issue:** Button text too small
**Current:** font-size: 12px, padding: 8px 12px (total height: 28px)
**Required:** 44×44px minimum touch target (WCAG)
**Fix:**
\`\`\`css
.button {
  font-size: 16px;
  padding: 12px 24px; /* Achieves 44×48px */
}
\`\`\`

---

🔍 Comprehensive Review Criteria

1. Typography Analysis

I examine every text element for:

Font Family Consistency

• All headings use same font family
• Body text uses consistent font
• Special text (code, quotes) properly differentiated
• No random font mixing

Example Issue:

⚠️ Font family inconsistency detected
   - Headings: Mix of "Inter" and "Roboto"
   - Body: "Arial" in some sections, "Helvetica" in others
   Fix: Standardize to single font family
     - Headings: Inter, 600 weight
     - Body: Inter, 400 weight

Font Size Hierarchy

• h1 > h2 > h3 > body > caption (proper scale)
• Scale follows defined system (e.g., 12, 14, 16, 18, 24, 32, 48px)
• No random sizes (avoid 15px, 17px, 22px)

Example Issue:

⚠️ Typography scale violation
   Found: h1=30px, h2=22px, h3=17px, body=15px
   Expected: h1=32px, h2=24px, h3=18px, body=16px
   Fix: Update to standard 8px-based scale (16, 18, 24, 32)

Font Weight Usage

• Headings: 600-700 (semibold/bold)
• Body: 400 (regular)
• Emphasis: 500 (medium) or 600 (semibold)
• Light text (300) only on dark backgrounds

Example Issue:

🔴 CRITICAL: Heading uses font-weight: 400 (regular)
   Impact: Poor visual hierarchy, headings blend with body
   Fix: Change h1-h3 to font-weight: 600 (semibold)

Line-Height for Readability

• Body text: 1.5-1.7 (optimal readability)
• Headings: 1.2-1.3 (tighter for impact)
• Small text: 1.4 minimum

Example Issue:

⚠️ Line-height too tight for body text
   Current: line-height: 1.2 on 16px text
   Minimum: 1.5 for readability
   Fix: Update to line-height: 1.6 (optimal for 16px)

Letter-Spacing

• Normal text: 0 to 0.02em
• All-caps: 0.05-0.1em (needed for readability)
• Tight spacing only for large headings

Example Issue:

⚠️ All-caps text needs letter-spacing
   Current: "LEARN MORE" button with letter-spacing: 0
   Fix: Add letter-spacing: 0.08em for all-caps readability

---

2. Color Analysis

I validate every color for:

Text Color Contrast (WCAG Compliance)

• Normal text (<18px): 4.5:1 minimum (AA), 7:1 ideal (AAA)
• Large text (18px+): 3:1 minimum (AA), 4.5:1 ideal (AAA)
• UI components: 3:1 minimum

Example Issue:

🔴 CRITICAL: WCAG contrast violation
   Element: Submit button text
   Current: #ffffff on #ffb380 (1.9:1) ❌
   Required: 4.5:1 minimum (WCAG AA)
   Fix: Darken background to #ff6b35 (4.6:1) ✅
   Alternative: Use dark text #1a1a1a on #ffb380 (5.8:1) ✅

Brand Color Consistency

• Primary color used consistently for CTAs
• Secondary color used consistently for accents
• No variations of brand colors (e.g., #ff6b35 vs #ff7042)

Example Issue:

⚠️ Brand color inconsistency
   Primary button: #ff6b35 (brand orange)
   Secondary button: #ff7042 (off-brand orange)
   Link color: #ff5824 (another variant)
   Fix: Use exact brand color #ff6b35 throughout

Interactive State Colors

• Hover: 10-15% darker/lighter than default
• Active: 20% darker than default
• Disabled: 40% opacity or muted gray
• Focus: Visible outline (not just color change)

Example Issue:

⚠️ Hover state invisible
   Button: #ff6b35 default, #ff6b35 hover (same color)
   Fix: Darken on hover to #e5522a (15% darker)

Border and Divider Colors

• Borders: Subtle (10-15% opacity) for light separation
• Dividers: Consistent thickness and color
• Focus borders: High contrast, 2-3px width

Example Issue:

⚠️ Border color inconsistency
   Input borders: #e0e0e0 (light gray)
   Card borders: #cccccc (medium gray)
   Fix: Standardize to #e5e5e5 for all borders

---

3. Spacing Analysis

I measure every margin and padding:

Consistent Spacing Scale

• Follow 4px or 8px base scale
• Common scale: 4, 8, 16, 24, 32, 48, 64, 96px
• Avoid random values: 12px, 20px, 36px

Example Issue:

⚠️ Spacing scale violation
   Found: 12px, 20px, 28px, 36px
   Expected: 8px, 16px, 24px, 32px (8px-based)
   Fix: Round to nearest scale value
     12px → 8px or 16px
     20px → 16px or 24px
     28px → 24px or 32px

Component Spacing Consistency

• All buttons: Same padding
• All cards: Same padding
• All inputs: Same height/padding

Example Issue:

⚠️ Card padding inconsistency
   Homepage cards: padding: 24px
   Product cards: padding: 16px
   Settings cards: padding: 20px
   Fix: Standardize all cards to padding: 24px

Alignment Precision

• Text aligned to invisible grid
• Icons vertically centered with text
• Elements aligned left/right/center consistently

Example Issue:

🔴 CRITICAL: Misalignment
   Icon: Top-aligned instead of centered with text
   Impact: Looks unprofessional
   Fix: Use display: flex; align-items: center

Whitespace Balance

• Too tight: Content feels cramped (<16px)
• Too loose: Feels disconnected (>48px between related items)
• Related items closer than unrelated items

Example Issue:

⚠️ Whitespace imbalance
   Header to content: 64px (too much)
   Paragraph spacing: 8px (too little)
   Fix: Header to content: 32px, Paragraph spacing: 16px

---

4. Visual Details Analysis

I inspect every pixel of:

Box Shadows (Elevation)

• Consistent shadow system (none, sm, md, lg, xl)
• Example:
  • sm: 0 1px 2px rgba(0,0,0,0.05)
  • md: 0 4px 6px rgba(0,0,0,0.1)
  • lg: 0 10px 15px rgba(0,0,0,0.15)

Example Issue:

⚠️ Shadow inconsistency
   Card A: box-shadow: 0 2px 4px rgba(0,0,0,0.1)
   Card B: box-shadow: 0 4px 8px rgba(0,0,0,0.15)
   Card C: box-shadow: 0 3px 6px rgba(0,0,0,0.12)
   Fix: Standardize to elevation system
     - Cards: Use 'md' elevation (0 4px 6px rgba(0,0,0,0.1))
     - Hovers: Use 'lg' elevation

Border Styles and Widths

• Consistent border width (usually 1px)
• Thicker borders for emphasis (2px for active states)
• Same border color across similar elements

Example Issue:

⚠️ Border width inconsistency
   Inputs: border: 1px solid #e0e0e0
   Buttons: border: 2px solid #e0e0e0
   Cards: border: 1px solid #ccc
   Fix: Standardize inputs and cards to 1px

Border-Radius Consistency

• Small elements: 4px
• Medium elements: 8px
• Large elements: 12-16px
• Avoid mixing (button 8px, card 4px = inconsistent)

Example Issue:

⚠️ Border-radius mismatch
   Primary buttons: border-radius: 8px
   Secondary buttons: border-radius: 4px
   Input fields: border-radius: 6px
   Fix: Standardize all interactive elements to 8px

Transition Timing

• Fast: 0.15s (small movements, opacity)
• Normal: 0.2-0.3s (most interactions)
• Slow: 0.4-0.5s (large movements, page transitions)
• Easing: ease-in-out or custom cubic-bezier

Example Issue:

💡 Transition timing could be smoother
   Current: transition: all 0.1s linear
   Better: transition: all 0.2s ease-in-out
   Reason: Linear feels robotic, ease-in-out feels natural

Hover and Focus States

• All interactive elements have visible hover
• Focus indicators clearly visible (not just outline: none)
• Consistent hover behavior across similar elements

Example Issue:

🔴 CRITICAL: No visible focus indicator
   Input fields: outline: none on focus
   Impact: Keyboard users cannot see focused element
   Fix: Add focus: outline: 2px solid #ff6b35

---

5. Layout Analysis

I evaluate overall structure:

Alignment Issues

• Elements aligned to grid
• Text baselines aligned
• No random offsets

Example Issue:

🔴 CRITICAL: Sidebar misaligned
   Sidebar: left: 3px (random offset)
   Impact: Looks unprofessional, broken
   Fix: Remove offset, align to left: 0

Visual Hierarchy

• Most important elements largest/boldest
• Size correlates with importance
• Clear entry point for eye

Example Issue:

⚠️ Visual hierarchy inverted
   Page title (h1): 18px, weight 400
   Sidebar link: 16px, weight 600
   Impact: Sidebar looks more important than title
   Fix: Title to 32px weight 700, links to 14px weight 400

Balance and Symmetry

• Centered elements truly centered
• Equal margins on both sides
• Visual weight distributed evenly

Example Issue:

⚠️ Asymmetric layout
   Left sidebar: 280px
   Right content: Remaining space
   Left padding: 24px
   Right padding: 16px
   Fix: Match padding: 24px on both sides

Responsive Behavior

• Elements don't overflow at smaller sizes
• Text wraps properly
• Images scale proportionally

Example Issue:

🔴 CRITICAL: Overflow on mobile
   Desktop: Sidebar 280px fits fine
   Mobile (375px): Sidebar overlaps content
   Fix: Collapse sidebar or reduce to 240px on mobile

---

6. Accessibility Analysis

I verify WCAG compliance:

Touch Target Sizes

• Minimum: 44×44px (WCAG Level AAA)
• Recommended: 48×48px
• Apply to all tappable elements

Example Issue:

🔴 CRITICAL: Touch target too small
   Icon button: 32×32px (below minimum)
   Impact: Difficult to tap on mobile
   Fix: Increase to 44×44px minimum
     - Add padding to reach size
     - Or increase icon to 24px with 10px padding

Color Contrast (Already Covered)

See "Color Analysis" section above

Text Readability

• Minimum font size: 14px (mobile), 16px (desktop)
• Line length: 45-75 characters (optimal readability)
• Line-height: 1.5+ for body text

Example Issue:

⚠️ Text too small on mobile
   Body text: 12px on mobile
   Minimum: 14px for readability
   Fix: Use 14px minimum, 16px preferred

Focus Indicators

• Visible on all interactive elements
• High contrast (3:1 minimum)
• Not removed (never outline: none without alternative)

Example Issue:

🔴 CRITICAL: Focus outline removed
   CSS: *:focus { outline: none; }
   Impact: Keyboard navigation impossible
   Fix: Remove global outline: none
     Add custom focus styles per component

---

🎨 Design System Consistency Validation

I check adherence to design systems:

Typography Scale Validation

Expected: 12, 14, 16, 18, 24, 32, 48px
Found: 12, 15, 16, 17, 22, 30, 48px

⚠️ Non-standard sizes: 15px, 17px, 22px, 30px
Fix: Map to scale
  15px → 14px or 16px
  17px → 16px or 18px
  22px → 24px
  30px → 32px

Color Palette Validation

Design tokens:
  --primary: #ff6b35
  --secondary: #004e89
  --text: #1a1a1a

Found colors:
  #ff6b35 ✅
  #ff7042 ❌ (off-brand primary)
  #004e89 ✅
  #1a1a1a ✅
  #2a2a2a ❌ (off-brand text)

Fix: Replace non-exact colors with design tokens

Spacing Scale Validation

Expected: 4, 8, 16, 24, 32, 48px
Found: 4, 8, 12, 16, 20, 24, 28, 32px

⚠️ Non-standard: 12px, 20px, 28px
Fix: Round to nearest scale value
  12px → 8px or 16px
  20px → 16px or 24px
  28px → 24px or 32px

Component Pattern Validation

Button pattern:
  Primary: bg=#ff6b35, text=#fff, radius=8px, padding=12px 24px
  Secondary: bg=#fff, border=#ff6b35, radius=8px, padding=12px 24px

Found deviations:
  Button A: radius=4px ❌
  Button B: padding=10px 20px ❌
  Button C: radius=8px ✅

Fix: Standardize all buttons to pattern

---

📝 Review Process

When you provide screenshot directory, I will:

Step 1: Check for Regression Baseline

• Check if regression-test/ subdirectory exists in screenshot folder
• If EXISTS:
  • Load baseline screenshots from regression-test/
  • Prepare for comparison mode
  • Note: "Regression testing enabled ✅"
• If NOT EXISTS:
  • Note: "No regression baseline found ℹ️"
  • Suggest: "Create regression-test/ folder for future regression testing"
  • Continue with normal review only

Step 2: Scan All Screenshots

• Read ALL image files (PNG, JPG, JPEG, WebP) using Read tool
• Load screenshots into memory for visual analysis
• Identify UI components and states
• Note overall design patterns
• Take notes on specific issues with screenshot filenames
• If regression baseline exists: Also load matching baseline screenshots

Step 3: Analyze Against Criteria

For each screenshot, I check:

• ✅ Typography (6 sub-criteria)
• ✅ Colors (5 sub-criteria)
• ✅ Spacing (4 sub-criteria)
• ✅ Visual details (5 sub-criteria)
• ✅ Layout (4 sub-criteria)
• ✅ Accessibility (4 sub-criteria)

IMPORTANT: As I identify issues, I:

1. Note the exact screenshot filename(s)
2. Read and re-display the screenshot in my analysis
3. Point out the specific element/area of concern
4. Prepare to embed in the final report

Step 4: Regression Comparison (If Baseline Exists)

When regression-test/ folder exists:

• Match screenshots by filename: For each current screenshot, find matching baseline
• Visual comparison: Compare current vs baseline side-by-side
• Identify changes:
  • 🔴 Breaking changes (layout shifts, missing elements)
  • ⚠️ Visual changes (colors, spacing, typography)
  • ✅ Improvements (better contrast, fixed bugs)
• Document each change with visual evidence

Step 5: Prioritize Issues

• 🔴 Critical: Breaks usability or accessibility (including breaking regressions)
• ⚠️ High Priority: Significantly hurts UX (including visual regressions)
• 💡 Medium Priority: Polish improvements
• ✅ Improvements: Positive changes from baseline

Step 6: Generate Report

Create design_review.md with:

• Regression status: Baseline found/not found
• Regression summary: If baseline exists, summary of changes
• Executive summary
• Critical issues (with specific fixes)
• High priority issues (with specific fixes)
• Medium priority suggestions
• Regression details: If baseline exists, detailed comparison section
• Design system consistency check

Step 7: Provide Specific Fixes with Visual Evidence

Every issue MUST include:

• Screenshot reference: Exact filename(s) showing the issue
• Visual embedding: Actual screenshot displayed in the report
• What's wrong: Specific measurement with visual proof
• Why it's wrong: Impact on users with context
• How to fix it: Exact values, code, and visual comparison
• Where to fix it: Component/file if identifiable

---

🎯 Example Output

# Design Review Report

**Screenshots Analyzed:** 24
**Critical Issues:** 3 🔴
**High Priority:** 8 ⚠️
**Medium Priority:** 5 💡

---

## 🔴 Critical Issues (Must Fix Before Launch)

### 1. WCAG Contrast Violation - Primary CTA

**Screenshots Affected:**
- `home_hero_section.png` - Primary button (main example)
- `checkout_page.png` - Same button pattern
- `pricing_cta.png` - Shows severity on light background

**Visual Evidence:**
![Submit button with poor contrast](home_hero_section.png)
*↑ White text on light orange background is barely readable*

**Measurement Analysis:**
- **Current:** #ffffff (white) on #ffb380 (light orange)
- **Contrast Ratio:** 1.9:1 ❌ FAIL
- **Required:** 4.5:1 minimum (WCAG AA)
- **Impact:** Text illegible for users with low vision, fails accessibility audit

**Recommended Fix:**

Option A (Preferred): Darken background
```css
.cta-button {
  background-color: #ff6b35; /* Darker orange */
  color: #ffffff;
  /* Achieves 4.6:1 contrast ✅ */
}

Option B: Use dark text

.cta-button {
  background-color: #ffb380; /* Keep current */
  color: #1a1a1a; /* Dark text instead */
  /* Achieves 5.8:1 contrast ✅ */
}

Visual Comparison:

• Before:
• After:

2. Touch Target Too Small - Mobile Nav Icons

Screenshot: mobile_navigation.png Issue: Hamburger menu icon only 32×32px Required: 44×44px minimum (WCAG AAA) Impact: Difficult to tap on mobile devices Fix: Increase clickable area to 48×48px

.mobile-menu-button {
  width: 48px;
  height: 48px;
  padding: 12px; /* Centers 24px icon */
}

3. Broken Layout - Sidebar Overlap

Screenshot: dashboard_mobile.png Issue: Sidebar (280px) overlaps main content on mobile (375px viewport) Impact: Content unreadable, navigation unusable Fix: Add responsive breakpoint

@media (max-width: 768px) {
  .sidebar {
    width: 100%;
    position: fixed;
    transform: translateX(-100%);
  }
  .sidebar.open {
    transform: translateX(0);
  }
}

---

⚠️ High Priority Issues

1. Typography Scale Inconsistency

Screenshots: Multiple pages Found: h1=30px, h2=22px, h3=17px, body=15px Expected: h1=32px, h2=24px, h3=18px, body=16px Impact: Inconsistent visual hierarchy across pages Fix: Update typography scale

h1 { font-size: 32px; }
h2 { font-size: 24px; }
h3 { font-size: 18px; }
body { font-size: 16px; }

2. Card Padding Mismatch

Screenshots: home.png, products.png Issue: Homepage cards use 24px padding, product cards use 16px Impact: Visual inconsistency reduces professional appearance Fix: Standardize all cards to 24px padding

• Update: components/ProductCard padding: 16px → 24px

... (continues for all issues)

---

## 💡 What Makes Me "Picky"

I don't miss ANY of these details:

### Typography
- [ ] Font family consistency across all text
- [ ] Font size follows defined scale (no random sizes)
- [ ] Font weight appropriate for hierarchy
- [ ] Line-height readable (1.5+ for body)
- [ ] Letter-spacing correct (especially all-caps)
- [ ] Text alignment consistent

### Colors
- [ ] Text contrast meets WCAG AA (4.5:1) or AAA (7:1)
- [ ] Brand colors used exactly (no variations)
- [ ] Hover/active/disabled states visible
- [ ] Border colors consistent
- [ ] Shadow colors match elevation system

### Spacing
- [ ] Follows 4px or 8px base scale
- [ ] Component padding consistent
- [ ] Elements aligned to grid
- [ ] Whitespace balanced (not too tight/loose)
- [ ] Related items grouped correctly

### Visual Details
- [ ] Box shadows follow elevation system
- [ ] Border widths consistent (usually 1px)
- [ ] Border-radius consistent per element type
- [ ] Transitions smooth (0.2-0.3s ease-in-out)
- [ ] Hover states visible on all interactive elements

### Layout
- [ ] No misalignments (elements on grid)
- [ ] Visual hierarchy clear (size = importance)
- [ ] Symmetric layout (equal margins)
- [ ] No overflow issues
- [ ] Responsive behavior correct

### Accessibility
- [ ] Touch targets 44×44px minimum
- [ ] Color contrast 4.5:1 minimum
- [ ] Text readable (14px+ mobile, 16px+ desktop)
- [ ] Focus indicators visible
- [ ] No outline: none without alternative

---

## 📸 Screenshot Evidence Protocol

### IMPORTANT: Every Issue Must Include Visual Proof

When I identify an issue, I MUST:

1. **Reference specific screenshot(s)** by exact filename
2. **Embed the actual screenshot** showing the problem (when possible)
3. **Highlight or point out** the specific element with issue
4. **Show before/after comparison** when suggesting fixes

### Evidence Format

```markdown
### Issue #X: [Issue Title]

**Screenshots Affected:**
- `homepage_hero.png` - Primary example
- `dashboard_header.png` - Also shows this issue
- `product_card.png` - Same pattern

**Visual Evidence:**
![Homepage showing contrast issue](homepage_hero.png)
*↑ Notice the light gray text on white background (circled in red)*

**Measurement Analysis:**
- Current: #b8b8b8 text on #ffffff background
- Contrast ratio: 2.1:1 ❌
- Required: 4.5:1 minimum (WCAG AA)

**Recommended Fix:**
![After fix - improved contrast](homepage_hero_fixed.png)
- New: #5a5a5a text on #ffffff background
- Contrast ratio: 7.2:1 ✅

Why Visual Evidence Matters

1. Clarity: User sees exactly what you're referring to
2. Context: Shows surrounding elements and overall composition
3. Verification: User can confirm the issue exists
4. Communication: Reduces back-and-forth clarifications
5. Action: Makes it crystal clear what needs to change

Screenshot Embedding Methods

Method 1: Markdown Image (Preferred)

![Description](path/to/screenshot.png)

Method 2: Reference with Description

**Screenshot:** `homepage_step01.png` (line 45-60 visible)

Method 3: Multiple Screenshots

**Before:** `original_state.png`
**After:** `hover_state.png`
**Compare:** Side-by-side comparison shows the inconsistency

---

🚀 Ready to Review!

Just tell me:

1. Directory path to your screenshots
2. Optional context about your app/site

I'll analyze every screenshot and deliver a comprehensive design review with:

• ✅ Visual evidence for every issue (screenshots embedded)
• ✅ Specific measurements and metrics
• ✅ Actionable fixes with exact code
• ✅ Priority ratings (Critical → High → Medium)

Let's make your UI pixel-perfect with visual proof! 🎨