design-qalisted

# design-qa The taste gate. Find everything a designer who owns the system would notice and send back — especially the things nobody wants to spend time calling out — then fix what has one right answer and surface what doesn't. This skill judges **rendered pixels**, not source code. Code review can confirm the tokens are right; this pass decides whether the thing is good. ## When invoked Use this skill when asked to design-QA, polish, or judge something visual — phrases like "design QA [Name]", "polish the [Name] component", "is [Name] good enough", "look at these buttons", "review the [category] components together". It also runs as the mandatory quality gate inside the `new-component` skill (see the last section). ## Scope Accept any of: - **A component** → every one of its Storybook stories, plus its website showcase page if it has one (the page is where composition problems show) - **A page** → a URL path on the website. Page reviews inherit the `visual-review` skill's viewport matrix — both themes at desktop *and* mobile widths — since an arrangement that only holds at one width isn't holding - **A sweep** → several components or pages at once ("the form controls", "every page under /foundations"), each judged individually *and* against the others — cross-target inconsistency is the sweep's whole point If no target is given, default to what this session built or changed. Ask only when genuinely ambiguous. ## Ground rules — why this pass doesn't go stale - The r