plan-design-review

Review design plans to identify missing decisions on typography, spacing, and accessibility.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/CaltexBevo/ihe-pulse --skill plan-design-review-caltexbevo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-design-review
Source: https://github.com/CaltexBevo/ihe-pulse/tree/main/.claude/skills/gstack.bak/plan-design-review
Command: npx skills add https://github.com/CaltexBevo/ihe-pulse --skill plan-design-review-caltexbevo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies missing design decisions in a plan and ensures they are added before implementation, helping teams ship intentional, well-justified designs.

Core Features & Use Cases

  • Systematic critique of design plans to surface gaps, inconsistencies, and decision rails.
  • Focus on empty states, accessibility, responsive behavior, typography and spacing decisions, and alignment with design principles.
  • Use cases include reviewing a plan for a new product feature, a redesign, or a design system upgrade, and producing a concrete list of decisions to be added to the plan.

Quick Start

Open the plan file and request a design-review pass to add missing decisions.

Frequently Asked Questions about plan-design-review

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

FAQPage Schema
How do I review a design plan to find missing edge cases and accessibility gaps?

To review a design plan for missing edge cases and accessibility gaps, systematically critique the plan against design rails to surface incomplete decisions on empty states, responsive behavior, and UI interactions. This ensures explicit choices are recorded before implementation.

What is a design review plan and what does it cover?

A design review plan is a document specifying UI decisions across flows. It covers typography, spacing, component usage, empty states, accessibility, and responsive behavior to guarantee intentional, well-justified designs are shipped.

When do I need to run a UX review on my design system upgrade?

You need to run a UX review on a design system upgrade when you must surface missing choices and align component usage with design principles. It ensures explicit decisions on typography, spacing, and interactions are documented before development.

Can I use this approach to review a plan for a new product feature?

Yes, you can use this approach to review a plan for a new product feature. It systematically identifies gaps in design decisions and produces a concrete list of missing choices regarding edge-case handling and success criteria to add to the plan.

What's the best way to document explicit decisions on responsive behavior and empty states?

The best way to document explicit decisions on responsive behavior and empty states is to pass the design plan through a rigorous review. This surfaces missing choices and records them directly in the revised plan to ensure well-justified designs.