Design Review

Review a feature against the project's design system through three lenses, then consolidate the findings into one prioritized report. Small UI changes get a focused diff and headless browser check in the main session.

Apply three lenses: visual compliance, interaction quality, and component robustness.

When to Use

• The user requests a design review
• Substantial UI changes or new component patterns are ready for review
• When design system compliance is uncertain

Prerequisites

1. DESIGN.md (or equivalent) must exist in the repo — the agents need a spec to review against
2. Know which files changed — the agents need a focused file list