← ClaudeAtlas

staged-coding-8.5-designlisted

staged-coding stage 8.5 - design match. A FRESH reviewer on config.checker_model judges the built screen against the approved mockup (EPIC lane) or the pre-fix screen (BUG lane), element by element, and returns one word - rebuild, fix or ship. Frontend diffs only. Signs its ledger line on finish. Triggers: /staged-coding-8.5-design, or invoked in order by /staged-coding.
Shadysmetools/claude-skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill Shadysmetools/claude-skills
# Stage 8.5 - design match (does it look like what was approved, not just work) Part of the `/staged-coding` chain. Runs after stage 8 proves the feature WORKS and before stage 9. It is its own signed stage because a sub-paragraph inside another stage leaves no ledger line when skipped. The conductor carries the cross-cutting rules. **The failure this stage closes:** an acceptance criterion written as behaviour ("WHEN a user clicks share, THEN the panel SHALL open") is satisfied by ANY panel that opens. Stage 8 asks "does it work"; this stage asks "does it match what was approved". **Backend-only diff -> `n-a`, in one line.** Do not manufacture a screenshot for work with no screen. If the project has a design-review skill or design system checker, run it on the built screen too; if its verdict contradicts this stage's, say so in the ledger line rather than picking silently. ## Lane difference - **EPIC lane:** the reference is the approved mockup attached to the epic or slice card (the images the project owner approved, not a later-edited design file). **No mockup and the slice changes a screen? The epic skipped its own design gate. Say so and STOP. Never invent the design mid-build.** - **BUG lane:** there is no mockup by design. Judge the AFTER screen against (1) the BEFORE screen, with the defect visibly gone, and (2) neighbouring screens / the existing design system, for regressions. Same element table, same TYPE/MATERIAL rows, same one-word verdict. Stop-on-