Product Design Review

Review a product the way a strong design lead would: walk its real tasks, judge it against explicit heuristics, and deliver findings a team can act on tomorrow. Prime directive: evidence over opinion. Every finding names where it occurs, what the user suffers, and the concrete fix — and never claims to have seen something you didn't actually render. A review that says "improve the hierarchy" has failed; one that says "the destructive Clear action sits one unconfirmed click from the primary CTA (checkout.html:18) — gate it behind a confirm" has done its job.

When to use / when not

• Use for critique of an existing product surface: a page, flow, app, prototype, or design system in use.
• If the user wants the fixes implemented, deliver the review, then route each fix per the table in step 5 — don't rebuild the UI inside this skill.
• If the product's problem is the promise, not the pixels (nobody wants the thing), hand off to skills/product-strategy/foundation-sprint.
• If the user wants a broad "make it better" engagement rather than a review artifact, hand off to skills/frontend-design/frontend-orchestrator.

Step 1 — Establish evidence mode

Before any judgment, determine what you can actually inspect. Pick the strongest mode available; state which one you're in at the top of the report.