design-review

Reviews built interfaces against design briefs using screenshots and structured checklists.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/yashmishra2006/LexWrite-Website --skill design-review-yashmishra2006
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-review
Source: https://github.com/yashmishra2006/LexWrite-Website/tree/main/.agents/skills/design-review
Command: npx skills add https://github.com/yashmishra2006/LexWrite-Website --skill design-review-yashmishra2006

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After building a UI, it is hard to objectively verify that the implementation matches the intended design direction, works across breakpoints, and meets accessibility standards. This Skill runs a structured design critique that combines code inspection with mandatory visual screenshot analysis. ## Core Features & Use Cases - Brief-Aligned Review: Reads the feature's DESIGN_BRIEF.md and evaluates the built components against the stated aesthetic philosophy and requirements. - Mandatory Screenshot Capture: Captures full-page screenshots at mobile (375px), tablet (768px), and desktop (1280px) breakpoints via Playwright MCP or Cursor IDE browser, including dark mode and interactive states. - Comprehensive Checklist: Covers visual hierarchy, consistency, component quality, states, responsive behavior, accessibility (WCAG contrast, keyboard navigation, focus indicators), typography, and dark mode. - Use Case: After finishing a landing page, ask for a design review and receive a prioritized DESIGN_REVIEW.md with must-fix, should-fix, and could-improve items, each referencing specific files and screenshots. ## Quick Start Ask the assistant to run a design review of the feature you just built against its design brief, including screenshots at all breakpoints.

Frequently Asked Questions about design-review

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

FAQPage Schema
How do I run a design review on a page I just built?

Ask for a design review, critique, or QA pass after building. The Skill reads the feature's DESIGN_BRIEF.md, inspects the code, captures screenshots at mobile, tablet, and desktop widths, and produces a prioritized findings report.

What tools capture screenshots for a UI design review?

The Skill prefers the Playwright MCP server for viewport control and full-page captures, falls back to the Cursor IDE browser's screenshot tool, and as a last resort asks you to provide screenshots manually at 1280px, 768px, and 375px widths.

Does the design review check accessibility and WCAG compliance?

Yes. The checklist covers WCAG AA color contrast ratios, keyboard navigation, visible focus indicators, semantic HTML structure, alt text, and reduced-motion support, alongside visual and responsive checks.

Where are design review screenshots and reports saved?

Screenshots go to .design/<feature-slug>/screenshots/ with descriptive filenames encoding page and breakpoint. The final review is saved as DESIGN_REVIEW.md next to the feature's DESIGN_BRIEF.md, or in the project root if no .design folder exists.

What happens if no design brief exists for the review?

The Skill looks for .design/<feature-slug>/DESIGN_BRIEF.md first, then a root-level DESIGN_BRIEF.md. If neither exists, it asks you to describe the intended design direction before proceeding with the critique.