Build a UI decision system with ak:ui-ux-pro-max

Use ak:ui-ux-pro-max to choose and review product UI direction: layout, style, color, typography, interaction, accessibility, responsive behavior, forms, charts, and performance. Its search tools use packaged CSV datasets, so the recommendations are reproducible within a release and are not live standards.

Choose ak:ui-ux-pro-max for design reasoning

Use it when

• You are designing or reviewing a page, component, design system, navigation, animation, form, chart, or mobile interaction.
• You need a reasoned style, palette, typography, landing-page, or product-pattern recommendation before writing code.
• You want a prioritized UX and accessibility review with explicit anti-patterns.
• You want to persist a master design system and page-specific overrides.

Choose another workflow when

• You are ready to add shadcn/ui components or Tailwind implementation. Use ak:ui-styling after the direction is approved.
• You only need a terse audit against current live web guidelines. Use ak:web-design-guidelines.
• The task is backend-only, infrastructure-only, or has no visual or interaction consequence.

Prepare the product context

• State product type, audience, key tasks, platforms, content density, brand constraints, accessibility target, supported themes, and target devices.
• Provide existing screenshots, tokens, components, analytics, and known UX problems when available. Separate evidence from aesthetic preference.
• Install Python to run the bundled search CLI. Search itself requires no network.
• Define whether the run may write under design-system/; without persistence, the CLI only prints output.

Run the Skill

/ak:ui-ux-pro-max "Design an accessible mobile-first checkout system for a subscription app; preserve the existing brand, cover loading/error/empty states, dark mode, reduced motion, and provide implementation-ready tokens"

/ak:ui-ux-pro-max "Design an accessible mobile-first checkout system for a subscription app; preserve the existing brand, cover loading/error/empty states, dark mode, reduced motion, and provide implementation-ready tokens"

$ak:ui-ux-pro-max "Design an accessible mobile-first checkout system for a subscription app; preserve the existing brand, cover loading/error/empty states, dark mode, reduced motion, and provide implementation-ready tokens"

The Skill has no documented top-level mode flags. Its bundled search CLI does:

Follow the observable stages

1. Frame the product. Capture audience, platform, primary action, content, brand, constraints, and measurable usability outcomes.
2. Generate a baseline system. Start from the combined design-system search, then inspect the reasons and anti-patterns instead of treating the first match as a mandate.
3. Deepen uncertain areas. Search focused domains for accessibility, interaction, charts, typography, performance, or platform behavior.
4. Resolve conflicts. Project evidence, official requirements, and tested user needs take precedence over a packaged recommendation.
5. Persist only the approved system. Write the master and page override files after names, paths, tokens, and exceptions are agreed.
6. Implement and verify elsewhere. Use the project implementation workflow, then test the actual UI and report evidence.

Keep authority and freshness visible

• --persist writes design-system files; it does not implement components or prove that existing code follows them.
• A palette suggestion is not contrast evidence. Test actual foreground and background pairs in both themes and every interactive state.
• Do not overwrite an established design system without comparing tokens and documenting migration impact.
• Search commands have no provider cost or network effect. Later font loading, asset retrieval, implementation, or testing may.

Verify outputs and evidence

A complete result should include product assumptions, selected and rejected directions, semantic tokens, type and spacing scales, responsive behavior, component states, navigation rules, accessibility requirements, and page-level exceptions. Verify the implemented UI with keyboard and screen reader flows, touch targets, contrast, zoom or Dynamic Type, reduced motion, light/dark themes, small-phone and landscape layouts, loading and failure states, and chart table or text alternatives.

Stable and beta contain identical ak:ui-ux-pro-max Skill, scripts, and bundled datasets in the documented releases. Continue with Runtime adapters, Projects, artifacts, and checkpoints, or the Engineer Kit overview.