Design — Audit

Find what's broken in an EXISTING interface and prioritize fixes by impact. The output is a ranked, actionable issue list — not a vibe check. Every issue ties back to the user's goal, so you're fixing what matters, not nitpicking pixels.

When to use

• An existing screen/flow/site needs critique before iterating.
• "Why is conversion/completion low here?"
• Pre-redesign baseline: what to keep, what to fix.

When NOT to use

• Nothing's built yet → design-ideate / design-get-context.
• You want competitor benchmarks → design-research.
• Final conformance check on a prototype you just built → design-qa (compares to a spec; audit is open-ended).

Inputs

• Target: live URL, screenshot/image, or component path.
• ./design/context.md (goal, user, success) if it exists — anchors severity.