agentsclimarketplace

Design review process

Skill Infrasity-Labs/dev-gtm-claude-skills/.claude/skills/design-review-process

Open-source Claude skills for GEO, AI discoverability, and developer GTM workflows. Built for developer-focused companies that want their documentation to be found, parsed, and cited by AI systems.

Install
npx -y skills add Infrasity-Labs/dev-gtm-claude-skills --skill design-review-process

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

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

SKILL.md

1.7 KB, 328 tokens by cl100k_base, as published. Nobody here has run it

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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,984. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.