domains / families / design / design-review

design-review

combined

Review a web app or page for visual design quality — layout, typography, spacing, colour, hierarchy, consistency, interaction patterns, and responsive behaviour. Not a UX audit (that checks usability) — this checks whether it looks professional and polished. Produces a design findings report with screenshots. Triggers: 'design review', 'does this look good', 'review the design', 'check the layout', 'is this polished', 'visual review', 'design audit', 'make it look better', 'it looks off'. Review or audit a design/UI across 6 weighted dimensions with Nielsen's 10 heuristics and a prioritized findings table. Use when the user wants a design critique, quality score, heuristic evaluation, or audit of an existing screen, page, or product before/after build.

When to use

• Before showing something to a client or team
• When something "looks off" but you can't pinpoint why
• After building a feature, before calling it done
• Periodic quality check on a shipped product
• After a UX audit — this is the visual companion

When not to use

• UX audit
• usability checks
• workflow analysis
• friction analysis

Skill page

Conflict

The two skills share the name and the high-level goal of reviewing a web UI, but they define different procedures. The jezweb copy is a visual-polish checklist (layout, typography, color, hierarchy, component consistency, interaction) that produces a findings report with screenshots and explicitly excludes usability. The plugin87 copy is a scored heuristic audit (6 weighted dimensions, Nielsen's 10 heuristics, WCAG/contrast scripts, anti-slop taste file) that produces a weighted score and prioritized findings table. Neither copy contains the other's core steps, so crowning one would hide a real alternative.