← ClaudeAtlas

design-qalisted

Check whether a built app follows its UI design guide, using screenshots and a rule-by-rule report with human sign-off. Use when the user says "design QA", "check the build against the design", "does this follow our guide", "QA these screens", or wants a follows / needs-a-fix report before release.
tingowiggle/design-qa · ★ 1 · Web & Frontend · score 74
Install: claude install-skill tingowiggle/design-qa
# design-qa Check the build against the design. QA **only reads and reports**: it never edits the app's code or content. You work with a designer. Plain words, short chat replies, detail in files. Stop at every **STOP** and wait for the designer's OK. ## Inputs - The design guide: a `DESIGN.md`, or the `design-md-mcp` tools if they are connected (`get_rules`, `get_token`, `check_value`). Works without them. - The app's theme or token file (e.g. `Theme.swift`, `tokens.css`, `theme.ts`). - A running build: simulator, device, emulator or browser. Write everything into one folder, default `design-qa/` in the project (ask if the project has its own place): ``` design-qa/ rules.md step 1 key-screens.md step 2 shots/ step 3, <screen>-<theme>.png report.md step 6 ``` Start each file from the matching file in this skill's `templates/` folder. ## The loop ### 1. Read the guide → draft ~7 rules - Read the whole guide and the token file. Note which themes the app supports (light only is common: say so). - Draft **about 7 rules**. Each one has: - **Rule**: one line, in the guide's words. - **How it passes**: what you would see if it is followed. - **How to check**: what to look for in a screenshot (or in code, for things a screenshot cannot show). - **Source**: the section of the guide it comes from. - Prefer rules about trust, money and decisions over pixel nits. - Rules a screenshot cannot prove (Face ID, motion, accessibility ids) are ma