cubetiq/design-audit

Design Audit Workflow

What this workflow does

Reviews an existing interface for hierarchy, information architecture, interaction cost, consistency drift, accessibility, motion or performance waste, and component-boundary issues, then prioritizes fixes.

When to use

Use this when the product is built enough to inspect and the user wants critique or remediation guidance.

Agent chain

reviewer

Step details

1. Use frontend-design to restate the intended direction and lock the style contract assumptions the audit will judge against.
2. Use design to identify the primary failure dimensions before proposing fixes.
3. Inspect the relevant screens or UI implementation.
4. Return prioritized findings with concrete remediation guidance and the corrected direction.

Skill routing

• frontend-design for the public UI-design frame and intended direction
• design for critique taxonomy and route selection after diagnosis
• web-ui-design, mobile-ui-design, or desktop-ui-design for the remediation route once the audit identifies the failing surface

Context notes

Provide screenshots, page routes, or component references and note whether the ask is critique-only or critique plus implementation.

Verification

The result should prioritize specific issues rather than offering generic taste-based feedback.

Output contract

DESIGN_AUDIT_WORKFLOW_RESULT:
  corrected_direction: <2-5 word direction>
  findings:
    - severity: high | medium | low
      dimension: hierarchy | information_architecture | interaction_cost | consistency_drift | accessibility | motion_performance | component_boundary
      issue: <problem>
      fix: <recommended action>
  removals:
    - <what to remove or reject>
  strengths:
    - <what already works>

Follow-up items

Typical next step: /design-screen or /implement