Develop UI/UX guidance with ak:ui-ux-pro-max

Use ak:ui-ux-pro-max for UI structure, visual direction, interaction patterns, responsive behavior, accessibility guidance, and interface quality review. It searches bundled datasets and can synthesize a design-system recommendation; implementation remains a separate decision.

Choose ak:ui-ux-pro-max for guidance and review

Use ak:ui-ux-pro-max when

• You need product, style, color, typography, landing, chart, UX, icon, web, or React guidance from the packaged knowledge.
• You want a design-system recommendation before writing code.
• You are reviewing accessibility, interaction, responsive behavior, forms, navigation, charts, or theme consistency.
• You want to persist an approved recommendation for later page work.

Choose another workflow when

• You need working interface code. Use ak:frontend-design.
• You need a current upstream rules audit with file:line findings. Use ak:web-design-guidelines.
• You need formal token files and component specs. Use ak:design-system.
• You need campaign or brand visuals. Use ak:design.

Prepare the decision context and runtime

Provide the product type, audience, usage context, platform, stack, brand source, target screen or flow, current problems, supported themes and viewports, and whether the run may write recommendation files. Supply real user evidence when available; bundled recommendations do not replace it.

Complete Onboarding and review Runtime adapters.

Run the Skill

/ak:ui-ux-pro-max Recommend a design system and UX checklist for a mobile-first B2B campaign dashboard used in bright office environments. Use the approved brand guide, cover keyboard, touch, contrast, reduced motion, empty and error states, and do not write files or implement code

/ak:ui-ux-pro-max Recommend a design system and UX checklist for a mobile-first B2B campaign dashboard used in bright office environments. Use the approved brand guide, cover keyboard, touch, contrast, reduced motion, empty and error states, and do not write files or implement code

$ak:ui-ux-pro-max Recommend a design system and UX checklist for a mobile-first B2B campaign dashboard used in bright office environments. Use the approved brand guide, cover keyboard, touch, contrast, reduced motion, empty and error states, and do not write files or implement code

The packaged search helper supports --design-system, --domain, --stack, --max-results or -n, and --json. Design-system output uses --format or -f with ascii or markdown. These are helper options, not Skill flags.

Persistence is opt-in with --persist. --project-name or -p determines the project slug; --page adds a page override, and --output-dir or -o changes the base directory. Actual output is design-system/<project-slug>/MASTER.md and, when requested, design-system/<project-slug>/pages/<page-slug>.md.

Understand the stages

1. Frame the decision. The workflow records product, audience, platform, brand, screen, constraints, evidence, and whether you need advice or review.
2. Search local knowledge. BM25 search selects rows from bundled domains. A design-system run combines product, style, color, landing, and typography matches with packaged reasoning rules.
3. Synthesize the recommendation. Output can include pattern, section order, CTA placement, style, colors, typography, effects, anti-patterns, and a pre-delivery checklist.
4. Add focused guidance. Domain searches can deepen accessibility, forms, charts, interaction, responsive behavior, icons, or React topics.
5. Review against reality. You compare every recommendation with brand assets, user evidence, platform conventions, content, and current code.
6. Persist only if approved. The helper writes a Master file and optional page override; it does not implement the UI.

Keep guidance separate from mutation

The Skill does not authorize implementation, package installation, font or asset downloads, external research, analytics access, account changes, publication, Git operations, or deployment. Approve those separately.

Verify the outputs and evidence

A useful result should name the query, matched source domains, recommendation, reasoning, accessibility and responsive checks, known uncertainty, and any file written. Verify contrast with actual colors, typography with the required language, layouts with real content and viewport sizes, all interaction states, keyboard and screen-reader behavior, touch targets, and reduced motion.

Do not treat a checklist line or CSV field labeled performance or accessibility as measured evidence.

Troubleshoot or continue

Continue with the Marketing Kit overview or Projects, artifacts, and checkpoints.

Know the current limits

• Stable and beta contain byte-identical ak:ui-ux-pro-max content in the inspected releases.
• The source description names many technology stacks, but the executable stack-specific lookup in these releases exposes only react-native. Generic domains still include web and React-oriented records.
• Dataset counts and rule wording describe bundled release content, not completeness, freshness, quality, or standards compliance.
• The generator can fall back to generic patterns and values when local search finds no match. A formatted recommendation is not proof of relevance.
• Persisted Markdown includes generated guidance and timestamps. Review it before treating it as a project source of truth.