plan-design-review

# Plan Design Review. 0-10 Rate-Each-Dimension Method ## Why this exists A plan with UI/UX components is usually 3-5/10 on design completeness even when it reads "complete." Backend behavior is specified down to the function name; what the user sees is one sentence. Result: mid-build discovery that empty states, error states, loading states, and mobile breakpoints were never decided. This skill rates the plan's design dimensions 0-10 across 7 passes, explains what a 10 looks like, then EDITS THE PLAN to get there. Output is a fixed plan, not a comment thread. Complement to the `frontend-design` plugin (which generates designs from specs). This skill REVIEWS the design layer of a plan BEFORE the plugin generates anything. ## When to fire - Pre-implementation when the plan has any UI / UX / visual / interaction component - Deck / proposal / landing page work before render - Skills + tools that output to a human surface (chat message format, dashboard, status display) - When the operator says "review the design plan" or "what's the design rubric here" Skip for pure backend / API / infrastructure work with no human-facing surface. ## Pre-reading (consult once before Step 0) Read these sections of `knowledge/gstack-cross-cutting-patterns.md`: - §2 Cognitive Patterns. How Great Designers See (12 perceptual instincts) - §3 UX Principles. Three Laws of Usability + behavioral patterns + Goodwill Reservoir - §1 The structured-user-question decision-brief format (anti-batch rul...