Skip to content
cccskills
FreePublished on GitHub

design-review-process

Build a consistent process for reviewing design work from concept through implementation. Define checkpoints, review criteria, checklists, and approval steps, adapting the process to each project's size and risk.

OriginalShow the original description

Establish review gates — criteria, checkpoints, and approval flow. Use when work ships without consistent review. For running one individual session, use `design-critique`.

Run score Not tested

See how to install

Good for

  • Standardizing design reviews across a team
  • Preparing checklists before developer handoff
  • Defining review responsibilities and approval steps
  • Checking implemented screens against design specifications

Files included (1)

  • SKILL.md1.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

a-b-test-design

FreeSummary

Plan A/B experiments to measure the effect of a design change. Define a hypothesis, control and treatment versions, success metrics, sample size, and duration, with supporting measures to detect unintended consequences.

  • Planning a comparison between current and proposed designs
  • Defining success metrics for a change
  • Estimating sample size and test duration
Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Assess an existing interface against WCAG 2.2 accessibility guidelines. Identify barriers in content and interactions, rate their severity and user impact, and document affected locations, remediation steps, and code examples to guide improvements.

  • Reviewing accessibility in an existing design or build
  • Checking keyboard access and assistive technology compatibility
  • Prioritizing fixes by severity and user impact
Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Plan accessibility testing with people who use assistive technologies, such as screen readers and voice control. Define participant criteria, test environments, session procedures, coverage of WCAG accessibility guidelines, and a consistent format for reporting issues.

  • Planning test sessions with assistive technology users
  • Defining participant recruitment criteria
  • Mapping key user flows to test environments
Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Review visual consistency to understand how an interface shapes trust and perceived ease of use. Examine spacing, alignment, typography, and overlooked screen states to guide visual improvements alongside usability testing.

  • Investigating poor feedback on a functional interface
  • Checking visual consistency before launch
  • Reviewing error, empty, and loading states
Owl-Listener/designer-skills3KUpdated Sep 6, 2026

affinity-diagram

FreeSummary

Turn interview notes, observations, and survey responses into themes and actionable research insights. Group related evidence without preset categories, retain participant references, and prioritize findings by their impact on design decisions while noting patterns found in only one interview.

  • Synthesize findings across multiple interviews
  • Organize observation notes and survey responses
  • Prioritize research insights for design decisions
Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Refine a specific interface animation by choosing easing, meaning changes in speed, along with duration and movement order. Use it to tune buttons, modals, transitions, or loading indicators so motion guides attention and communicates changes.

  • Tune how a modal enters and exits
  • Adjust button and toggle animations
  • Coordinate the order of related movements
Owl-Listener/designer-skills3KUpdated Sep 6, 2026

See all skills by Owl-Listener

Report a problem with this skill