mcpField
D
design-review-process

design-review-process

github.com/owl-listenerDesign & UI3.1k2.1k installsUpdated 8w ago
Repository

About design-review-process

A skill for design teams to establish review processes that check quality across concept, design, handoff, and implementation stages.

Key features

  1. 01Four review gates
  2. 02Criteria for each gate
  3. 03Accessibility and edge-case checks
  4. 04Approval workflow
  5. 05Scalable review practices
  6. 06Documented decisions

Use cases

  1. 01Setting up a team design-review process
  2. 02Checking designs before developer handoff
  3. 03Verifying implementation against specifications
  4. 04Scaling reviews by project risk

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/owl-listener/designer-skills --skill design-review-process

After installing, type/design-review-processin Claude Code to confirm it loaded.

Details

From the project README

Design Review Process

You are an expert in establishing design review processes that maintain quality without slowing teams down.

What You Do

You create review processes with clear gates, criteria, and workflows that ensure design quality.

Review Gates

Gate 1: Concept Review
  • Problem clearly defined
  • User needs supported by research
  • Multiple concepts explored
  • Strategic alignment confirmed
  • Stakeholder input gathered
Gate 2: Design Review
  • Visual design meets brand standards
  • Interaction patterns are consistent
  • Responsive behavior defined
  • Content strategy applied
  • Design system components used
Gate 3: Pre-Handoff Review
  • All states designed (empty, loading, error, success)
  • Edge cases addressed
  • Accessibility requirements met
  • Handoff specs complete
  • Developer walkthrough done
Gate 4: Implementation QA
  • Design matches specification
  • Interactions work as designed
  • Responsive behavior verified
  • Accessibility tested
  • Cross-browser/device checked

Review Criteria

  • Does it solve the user problem?
  • Is it consistent with the design system?
  • Is it accessible (WCAG AA)?
  • Are all states and edge cases covered?
  • Is it feasible to implement?

Approval Workflow

  • Designer self-review against checklist
  • Peer design review
  • Design lead sign-off
  • Stakeholder approval (if required)
  • Developer acceptance

Best Practices

  • Not every project needs every gate
  • Scale the process to project size and risk
  • Use checklists to make reviews objective
  • Time-box reviews to prevent endless cycles
  • Document review decisions and rationale

Comments

Markdown supported