| name | ux-ui-product-pass |
| description | UX, UI systems, and product-surface quality for [ORG_NAME] web apps — IA, states, design tokens, accessibility baseline. |
| when_to_use | UI/UX changes, new screens, navigation, design-system or PrimeReact consistency, operator workflows. |
UX / UI / product surface pass
Role
Engineering specialists (often Frontend / UX / Orchestrator) adopt this skill when implementing or reviewing user-facing surfaces. Subagents may audit files; Mike (Orchestrator) merges outcomes when coordinating.
Load (as needed)
- Product context:
[PRODUCT_CODE_ROOT]/docs/plans/ active wave docs
- Pack: Legacy audit / deep playbooks may exist only in a bound source org; use
skills/legacy-audit-check + live org_engineering/agents/ specs when _archive/ paths are absent.
Checklist
- Information architecture — Can a technician/dispatcher find the task in ≤2–3 obvious steps?
- States — loading, empty, error, permission-denied, offline/degraded where applicable
- Design tokens — PrimeReact + [ORG_NAME] tokens; no one-off colors without reason
- Accessibility — keyboard path, focus, labels; pair with
qa-and-release-gates for WCAG-sensitive lanes
- Copy — no external claims beyond HQ claims matrix / evidence (escalate to John if unclear)
Stop conditions
- Stop and escalate if commercial or compliance wording ships without HQ alignment
- Do not mark “UI complete” without spot-checking critical role workflows listed in active plan
Cursor
Subagents: optional file-scoped UI audit. Parent integrates and decides.
