design-review

Audit live sites for visual inconsistencies and apply fixes with atomic commits.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/singhianand23045/GarryTan --skill design-review-singhianand23045
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-review
Source: https://github.com/singhianand23045/GarryTan/tree/main/design-review
Command: npx skills add https://github.com/singhianand23045/GarryTan --skill design-review-singhianand23045

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design-review identifies visual inconsistencies, spacing issues, hierarchy problems, AI slop patterns, and slow interactions, then fixes them iteratively to improve product polish.

Core Features & Use Cases

  • Visual QA pass across pages and components to ensure typography, spacing, and alignment are consistent.
  • Plan-mode design review before implementation and post-release polish with before/after verification.
  • Atomic commits of fixes accompanied by before/after screenshots to track progress.

Quick Start

Describe the target site and run /design-review to start a visual audit and apply 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 a live frontend site?

A visual QA audit identifies typography, spacing, and alignment inconsistencies by analyzing live frontend pages and components, then iteratively applies fixes to improve overall product polish.

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

The best way to fix layout hierarchy problems is through an iterative design review that detects visual inconsistencies and applies corrections with atomic commits and before/after screenshots for verification.

Can I use automated design reviews for post-release polish across multiple components?

Yes, you can use automated design reviews for post-release polish. The process enforces fixes with atomic commits and re-verifies them in context using before/after screenshots across pages and components.

How does visual QA handle AI slop patterns and slow interactions?

Visual QA handles AI slop patterns and slow interactions by identifying these specific issues during the audit, then iteratively fixing them to improve the visual consistency and responsiveness of the site.

Do I need to provide before and after screenshots for design fixes?

You do not need to manually provide screenshots; the design review process automatically generates before and after screenshots to verify fixes and track progress through atomic commits.