design-verifylisted
Install: claude install-skill rterakedis/leanwheel-skills
# Design Verify Skill
**Goal:** Confirm that user-visible UI changes actually match the design contract — by rendering them, not by re-reading the code. Code review catches wrong logic; this catches wrong *pixels*: off-token colors, missing dark mode, broken states, truncated type.
**When:** Invoked inline by `/dev-story` after DoD passes for any story that changed user-visible UI, or directly via `/design-verify`. Skip entirely (report "no user-visible surface changed") for pure backend/refactor diffs.
**Verify reachability, not presence.** A string, control, or affordance existing in source is not evidence it can reach the screen — drive the app or dump the hierarchy. When an element can't be addressed in a UI test, dump the tree before blaming the tooling; the element may not render at all. Canonical: `dev-story` verification step.
**Requires:** `docs/ux/DESIGN.md` and/or `docs/ux/EXPERIENCE.md`. If neither exists, fall back to the platform guardrails checklist only (`docs/setup/swift/` or `docs/setup/web/`).
---
## Step 1 — Scope
1. Identify changed surfaces: from the story's File List (or `git diff --name-only` when standalone), list the screens/pages/components a user can see.
2. From `docs/ux/EXPERIENCE.md`, pull the required states for each changed surface (empty / loading / error / offline, per the State Patterns section).
3. From `docs/ux/DESIGN.md` frontmatter, pull the tokens the changed surfaces consume.
4. If the story has a `### Design Contract` section