design-review

Audit visual designs for inconsistencies, spacing, hierarchy, and slow interactions.

1|Updated May 27, 2026
One-click install
npx skills add https://github.com/mi179/claude-skills --skill design-review-mi179
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-review
Source: https://github.com/mi179/claude-skills/tree/main/user/gstack/design-review
Command: npx skills add https://github.com/mi179/claude-skills --skill design-review-mi179

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use /plan-design-review. Use when asked to "audit the design", "visual QA", "check if it looks good", or "design polish". Proactively suggest when the user mentions visual inconsistencies or wants to polish the look of a live site. (gstack)

Core Features & Use Cases

  • Visual QA audits of UI designs to catch spacing, typography, and hierarchy issues.
  • Propose concrete fixes and commit them atomically with before/after verification.
  • Plan-mode design review support and live-site polish suggestions.

Quick Start

Ask me to audit a page or design mockup and I will identify visual issues and propose fixes.

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 visual QA audit on my UI design mockups?

Visual QA audits identify inconsistencies, spacing problems, and hierarchy issues in UI mockups, style guides, or component libraries. The review process iteratively fixes issues in source code, committing each fix atomically and re-verifying with before and after screenshots.

What is the best way to fix spacing and hierarchy problems in a live web interface?

Fixing spacing and hierarchy problems in a live site requires iteratively adjusting source code and verifying with before and after screenshots. This process catches visual inconsistency, AI slop patterns, and slow interactions, ensuring traceable UI polish improvements through atomic commits.

Can I review design system components for visual consistency before implementation?

Yes, design system refinement is supported through plan-mode design review before implementation. This approach audits component libraries and style guides to catch typography and spacing issues, proposing concrete fixes before any code changes are made.

Do I need to provide source code for a design review to fix visual issues?

Yes, providing source code is necessary to fix visual issues. The Skill iteratively applies fixes directly in the source, requiring a disciplined workflow with atomic commits and before and after verification screenshots to ensure traceable improvements.

What visual problems does a design review catch when polishing a live site?

A design review catches visual inconsistencies, spacing issues, hierarchy problems, AI slop patterns, and slow interactions. It applies to live sites, design mockups, style guides, and component libraries to ensure polished, consistent design quality.

How does before and after verification work during UI polish?

Before and after verification works by capturing screenshots before a fix and after applying it to the source code. This iterative process ensures visual QA improvements are traceable and validated, with each adjustment committed atomically to maintain a clean workflow.