design-review

Audit UI designs for visual inconsistencies and fix them with atomic commits.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Ulanxx/mzstack --skill design-review-ulanxx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-review
Source: https://github.com/Ulanxx/mzstack/tree/main/design-review
Command: npx skills add https://github.com/Ulanxx/mzstack --skill design-review-ulanxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designer's eye QA identifies visual inconsistencies, spacing issues, typography hierarchy problems, AI slop patterns, and slow interactions, then fixes them with atomic commits and re-verification using before/after screenshots.

Core Features & Use Cases

  • Visual QA auditing: detect layout, spacing, color, typography issues across components.
  • Plan-mode design review: audit before implementation and propose fixes.
  • Automated verification: commit fixes atomically and re-run checks to verify improvements.

Quick Start

Run a design audit on the current project to generate a before/after evidence package and guide polish.

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 UI audit to fix visual inconsistencies and spacing issues?

Run a UI audit to detect layout, spacing, color, and typography issues across components, then apply fixes atomically and re-verify improvements using before/after screenshots.

Can I review designs in plan-mode before implementation to catch hierarchy problems?

Yes, you can review designs in plan-mode before implementation to audit for visual inconsistencies, hierarchy problems, and AI slop patterns, returning concrete proposed fixes to guide development.

What is visual QA for frontend designs and how does automated verification work?

Visual QA identifies spacing, typography, and interaction issues, then fixes them with atomic commits and re-runs checks using before/after screenshots to verify improvements.

How do I detect and fix AI slop patterns in my frontend UI?

Detect and fix AI slop patterns by auditing UI designs for visual inconsistencies and slow interactions, returning concrete fixes, committing them atomically, and verifying with before/after evidence artifacts.

Does this design review process work for live-site audits and proactive polish?

Yes, the design review applies to live-site audits and proactive polish when visual issues are mentioned, returning concrete fixes with atomic commits and before/after screenshot re-verification.