ss-review

# UI Design Review ## Registry-first artifact boundary When `.styleseed/project.json` and `.styleseed/artifacts/index.json` exist, resolve the requested artifact ID first, then read only `.styleseed/bundles/<artifact-id>.md` and `.styleseed/manifests/<artifact-id>.json`. Never fall back to the global legacy bundle for a registry project. Legacy projects may use `.styleseed/effective-rules.md` only when no registry exists. Read `.styleseed/effective-rules.md` and `.styleseed/manifest.json`. If missing or stale, invoke `/ss-resolve` or `$ss-resolve` from `STYLESEED.md` first. Review task fitness and grammar coherence before framework conventions. For non-web artifacts, replace React/Tailwind-only checks with the active adapter's render/export checks. ## When NOT to use - For accessibility-only issues → use `/ss-a11y` - For Nielsen UX heuristics → use `/ss-audit` - For a quick automated check → use `/ss-lint` - For non-UI code (data fetching, business rules) Review the file: **$ARGUMENTS** ## Checklist ### 1. Design Token and Recipe Compliance - [ ] No hardcoded hex colors (use semantic tokens: `text-foreground`, `bg-brand`, etc.) - [ ] No hardcoded px spacing in Tailwind (use `p-6` not `p-[24px]`) - [ ] Pattern geometry/elevation uses the selected recipe or explicit semantic variables - [ ] No hardcoded universal `rounded-2xl + shadow + mx-6` language across unrelated recipes ### 2. Component Conventions - [ ] Uses `data-slot` attribute - [ ] Uses `cn()` for className m...