Visual Review Pipeline

Visual Review Pipeline

Automated visual review: Aphrodite captures screenshots via Playwright MCP → Self-analyzes for visual issues → Addresses findings in a loop.

Overview

This pipeline establishes a formal workflow for detecting and resolving visual regressions and design issues. It enforces structured JSON output, iteration limits, and escalation criteria to prevent infinite fix loops.

Pipeline Flow

Aphrodite implements UI
    ↓
Playwright screenshot (browser/screenshotPage)
    ↓
Aphrodite self-analyzes (layout, contrast, responsive, accessibility)
    ↓
├─ verdict: pass → proceed to Themis review
├─ verdict: fail + iteration < 3 → fix → re-capture
└─ verdict: fail + iteration = 3 → Zeus escalation

Workflow Steps

Step 1: Capture

Aphrodite uses Playwright MCP to capture screenshots.

• Navigate to target URL or render component
• Capture full-page screenshot via browser/screenshotPage
• Capture viewport-specific screenshots for responsive checks
• Name files descriptively: screenshot-iteration-N-component.png

Step 2: Analyze

Aphrodite self-analyzes screenshots visually.

• Examine screenshot(s) for visual issues
• Identify problems in layout, contrast, responsive behavior, and accessibility
• Return findings in the structured JSON schema (below)
• Include iteration number in findings
• Mark issues with pass_if_fixed IDs

Step 3: Fix

Aphrodite addresses each finding from self-analysis.

• Triage findings by severity (critical → high → medium → low)
• Fix each issue in component code
• Commit changes with descriptive message
• Re-capture screenshot for next iteration

Step 4: Loop

Repeat Steps 1-3 for up to 3 iterations.

• Each iteration must fix at least one pass_if_fixed issue
• Track iteration count in findings object
• If no progress detected (zero fixes applied), escalate immediately
• Compare before/after screenshots to verify fixes

Step 5: Escalate

Zeus intervenes if issues persist after 3 iterations.

• Trigger: 3 iterations exhausted or zero-progress detected
• Action: Zeus coordinates manual review or architectural decision

JSON Schema

Aphrodite must return findings in this exact structure:

{
  "verdict": "pass | fail | warn",
  "iteration": 1,
  "max_iterations": 3,
  "issues": [
    {
      "id": "VIS-001",
      "category": "layout",
      "severity": "high",
      "description": "Sidebar overflows on viewport width < 768px",
      "screenshot_region": "left-panel at x:0,y:0 width:300px",
      "recommendation": "Add responsive breakpoint to collapse sidebar below 768px"
    }
  ],
  "summary": "One-line summary of overall visual state",
  "pass_if_fixed": ["VIS-001", "VIS-002"]
}

Field Definitions

Categories

Severity Levels

Iteration Rules

1. Minimum progress: Each iteration fixes at least one pass_if_fixed issue
2. No regression: Fixes must not introduce new issues
3. Track state: Include iteration count in findings JSON
4. Early exit: If verdict is pass, stop iterating
5. Immediate escalation: If zero issues fixed in an iteration, escalate to Zeus

Progress Detection

Iteration N:
  - Compare pass_if_fixed list to previous iteration
  - If any ID removed from pass_if_fixed → progress detected
  - If pass_if_fixed unchanged → zero progress → escalate

Escalation Criteria

Zeus must be invoked when:

1. 3 iterations exhausted — issues cannot be resolved within the pipeline
2. Backend/data dependency — issue requires API changes, data model updates, or backend fixes
3. Architectural issue — problem stems from component architecture, not CSS/styling
4. Zero progress — no pass_if_fixed issues resolved in an iteration
5. Conflicting fixes — resolving one issue introduces another

Escalation format:

@zeus Visual review escalation: [component] failed after [N] iterations.
Remaining issues: [list of unresolved pass_if_fixed IDs]
Root cause: [backend | architectural | conflicting]

MCP Requirements

Playwright MCP (Required)

• Use browser/screenshotPage for full-page captures
• Use browser/snapshot for accessibility tree context
• Fallback: If Playwright MCP is unavailable, skip with warning:

  ⚠️ Playwright MCP unavailable — visual review skipped.
  Install Playwright MCP server to enable visual review pipeline.
  

For UI implementation review, Aphrodite self-reviews.

Integration Points

• Code Review (Themis): Visual review runs as part of frontend code review; findings feed into Themis's verdict.
• Artifact Protocol: Visual review findings can attach to IMPL- artifacts. Escalation decisions documented in _notes/.
• Memory Bank: Recurring visual issues documented in 01-active-context.md. Architectural visual decisions recorded as _notes/NOTE000X-*.md.

Example Workflow

1. Aphrodite captures screenshot of LoginButton
   → screenshot-iteration-1-login-button.png

2. Self-analysis returns:
   {
     "verdict": "fail", "iteration": 1,
     "issues": [{
       "id": "VIS-001", "category": "contrast", "severity": "high",
       "description": "White text on light blue bg, contrast ratio 2.1:1",
       "recommendation": "Darken background to #1a56db"
     }],
     "pass_if_fixed": ["VIS-001"]
   }

3. Fix contrast, re-capture → screenshot-iteration-2-login-button.png

4. Re-analysis: { "verdict": "pass", "iteration": 2, "issues": [],
     "summary": "All visual issues resolved", "pass_if_fixed": [] }

5. Pipeline complete — 2 iterations, all issues fixed.