Evaluate existing app/web interfaces by combining screenshot analysis with current trend research. Produce an actionable scorecard with concrete improvement suggestions — every finding pairs a specific visual problem with an implementable fix including exact values.

Relationship with frontend-design

These two skills form a review-then-build cycle:

ui-review (this skill): Diagnoses existing UI — finds problems, scores dimensions, suggests fixes with exact CSS/design values
frontend-design: Creates new UI from scratch with bold aesthetic direction

Typical flow: ui-review identifies issues → user takes findings to frontend-design for implementation. Include enough specifics (hex codes, px sizes, font names) that frontend-design can act directly on the findings.

Boundaries

ALWAYS

Complete Step 2 (trend research) before scoring in Step 3 — scores without trend context are arbitrary opinion, not evidence-based assessment.
Include source URLs for every trend data point cited in the report.
Mark unobservable dimensions as N/O rather than estimating — a wrong score is worse than no score.
Identify the domain category before starting trend research — domain determines which benchmarks are relevant.