design-review

Evaluate proposed UI changes against project design notes for design system compliance.

6|1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/navapbc/digital-service-orchestra --skill design-review-navapbc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-review
Source: https://github.com/navapbc/digital-service-orchestra/tree/main/plugins/dso/skills/design-review
Command: npx skills add https://github.com/navapbc/digital-service-orchestra --skill design-review-navapbc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill helps teams ensure proposed UI changes align with the project design notes and design system before merging, reducing design drift and QA risk.

Core Features & Use Cases

  • Orchestrates multi-perspective design reviews using predefined reviewer prompts and scoring.
  • Binds inputs to design-notes and system architecture to produce structured, schema-compliant feedback.
  • Applies to code, wireframes, or screenshots to validate design consistency before implementation.

Quick Start

Invoke the design-review skill on a pull request to generate a structured, perspective-driven review.

Frequently Asked Questions about design-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate design QA reviews for UI changes before merging?▼

You can automate design QA by invoking this skill on a pull request to evaluate proposed UI changes against your design notes, ensuring design system compliance before merging.

What is a multi-perspective design review and how does it work?▼

A multi-perspective design review evaluates UI changes using six predefined reviewer perspectives and scoring, binding inputs to your design notes to produce structured, schema-compliant feedback.

Can I review wireframes and screenshots for design system compliance?▼

Yes, you can review wireframes and screenshots for design system compliance, as the skill validates design consistency across code, visual mockups, and front-end implementations.

Does the design review process require predefined design notes?▼

Yes, the process requires predefined design notes because the skill binds your inputs to them and the system architecture to produce structured, schema-compliant feedback.

What is the best way to enforce design system consistency across front-end code?▼

The best way to enforce consistency is to apply a structured review protocol using predefined reviewer prompts and scoring to evaluate front-end code against your project design notes.

When should I not use an automated UI review protocol?▼

You should avoid automated UI review protocols when lacking established design notes, as the evaluation depends on binding inputs to existing project design notes and system architecture.