design-review

Audit live UI for visual inconsistencies and propose fixes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow helps designers and developers quickly identify visual regressions, spacing inconsistencies, and typography issues on live sites, then fixes them with atomic commits and visual verification.

Core Features & Use Cases

  • Visual QA for spacing, typography, contrast, and layout hierarchy on real pages.
  • Iterate fixes with before/after screenshots and commit each change atomically.
  • Plan-mode design review to discuss and plan design polish before implementation on a feature.

Quick Start

Request a design audit on the current page and apply the approved visual fixes.

Frequently Asked Questions about design-review

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

FAQPage Schema
How do I audit visual inconsistencies on a live site?

A visual audit scans a live site URL to detect spacing issues, typography problems, and hierarchy flaws, then proposes targeted fixes with before/after visual verification.

Can I review and plan UI polish before applying frontend fixes?

Yes, you can use plan-mode design review to discuss and plan UI polish on a feature before implementation, ensuring alignment with your design system reference before any code changes.

How do I fix spacing and typography issues with atomic commits?

You fix spacing and typography issues by iterating through a sequence of verify/fix steps, applying each change as an atomic commit to ensure before and after visuals align perfectly.

Do I need a design system reference to check UI hierarchy problems?

A design system reference is required if present in your project, as it provides the baseline standards needed to accurately evaluate UI hierarchy problems and propose visual fixes.

What is the best way to fix visual regressions on focused pages?

The best way to fix visual regressions on focused pages is to request a design audit on the specific URL, apply the approved visual fixes, and verify the results with before/after screenshots.