verify-ui

# Verify UI Verify a feature's UI implementation matches the Stitch design at the token level. Produces a two-source token audit (HTML ↔ Code) overlaid with an X-component default-render trap checklist, plus an X-components compliance check. **Architecture Reference:** @../_shared/patterns.md **Rationale & edge cases:** @RATIONALE.md *(read only when an edge case stumps you)* ## Prerequisites - Feature implemented (build passes) - `.claude/docs/_project/stitch-project.json` exists with a `features[{featurename}]` entry ## Workflow ``` [USER INVOKES] → Preflight → Acquire HTML (reuse or download) → Token Extraction → Catalog → Token Audit → Trap Checklist → Component Overrides Check → Motion Audit → X-Components Check → Present Results → Handle Mismatches → Cleanup → DONE ``` --- ## Step 1: Preflight 1. Parse feature name from `$ARGUMENTS` or ask the user. 2. Verify required tooling — **Python 3** (used by Step 3 to run `.claude/skills/_shared/extract_tokens.py`): ```bash python3 --version ``` If the command fails (`python3: command not found`, non-zero exit), **STOP** and tell the user: ``` Python 3 is not installed (or `python3` is not on PATH). /verify-ui extracts design tokens from Stitch HTML via `.claude/skills/_shared/extract_tokens.py` and cannot proceed without it. Install Python 3, then re-invoke /verify-ui {featurename}: - macOS: brew install python3 - Linux: sudo apt-get install python3 (or your distro's package ...