infrasity-labs/dev-gtm-claude-skills

design-review-process

Establish design review gates with criteria, checklists, and approval workflows.

First seen Jun 30, 2026

Installation

$ npx skills add infrasity-labs/dev-gtm-claude-skills --skill design-review-process

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from infrasity-labs/dev-gtm-claude-skills · top by installs.

npx skills add infrasity-labs/dev-gtm-claude-skills

Browse all from infrasity-labs/dev-gtm-claude-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Stars 123
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,728 B
  • docs SUMMARY.md 109 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 53 installs

SKILL.md

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