| name | ui-ux-pro-max |
| description | Design intelligence for producing professional UI/UX documentation across platforms (web, mobile, desktop). Use during the design phase of user-facing features to generate a persistent design system — tokens, component specs, layout, states, accessibility — and per-page design docs. Invoked by sdlc-design. Produces design-system/MASTER.md as the single source of truth for visual and interaction design. |
UI/UX Pro Max (design documentation)
Adapted from nextlevelbuilder/ui-ux-pro-max-skill. Generates design intelligence, not code.
Modes
--design-system — produce the master system (run this first).--persist — write outputs to disk instead of only chatting them (always use in SDLC).- per-page — generate a screen/flow spec that overrides the master where needed.
design-system/MASTER.md must contain
- Design tokens — color (with semantic roles), typography scale, spacing, radius, shadows.
- Component specs — for each component: anatomy, variants, sizes, states
(default/hover/focus/active/disabled/loading/error), do/don't.
- Layout — grid, breakpoints, responsive rules.
- Accessibility — contrast targets, focus order, keyboard, ARIA expectations, motion/reduced-motion.
- Content/voice — tone, capitalization, error-message style (Ukrainian, per policy).
Per-page docs (design-system/pages/.md)
- Purpose, entry/exit, states (empty/loading/error/success), responsive notes,
and which acceptance criteria from spec.md the page satisfies.
Rules
- Be platform-aware: don't apply mobile gestures to a desktop-only tool, etc.
- Every screen must trace to a spec acceptance criterion. Flag any orphan screens.
- Hand the page list back to
sdlc-design so it can append build tasks to tasks.md.
Примітка (UK)
Скіл генерує дизайн-документацію (не код). Головний артефакт — design-system/MASTER.md:
токени, специфікації компонентів зі станами, лейаут, доступність і тон комунікації
українською. Кожен екран має відповідати критерію приймання зі специфікації.
