Ai ui-ux-pro-max

install
source · Clone the upstream repo
git clone https://github.com/wpank/ai
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/wpank/ai "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/design-systems/ui-ux-pro-max" ~/.claude/skills/wpank-ai-ui-ux-pro-max && rm -rf "$T"
manifest: skills/design-systems/ui-ux-pro-max/SKILL.md
source content

UI/UX Pro Max

Searchable design database with CLI for generating complete design systems from natural language queries.

See also:

ui-design
for fundamentals and decision-making. This skill provides data-driven recommendations via CLI.

When to Use

  • Designing new UI components or pages
  • Choosing color palettes and typography
  • Reviewing code for UX issues
  • Building landing pages or dashboards
  • Implementing accessibility requirements

Rule Categories by Priority

PriorityCategoryImpactDomain
1AccessibilityCRITICAL
ux
2Touch & InteractionCRITICAL
ux
3PerformanceHIGH
ux
4Layout & ResponsiveHIGH
ux
5Typography & ColorMEDIUM
typography
,
color
6AnimationMEDIUM
ux
7Style SelectionMEDIUM
style
,
product
8Charts & DataLOW
chart

Quick Reference

Accessibility (CRITICAL)

  • color-contrast
    — Minimum 4.5:1 ratio for normal text
  • focus-states
    — Visible focus rings on interactive elements
  • alt-text
    — Descriptive alt text for meaningful images
  • aria-labels
    — aria-label for icon-only buttons
  • keyboard-nav
    — Tab order matches visual order
  • form-labels
    — Use label with for attribute

Touch & Interaction (CRITICAL)

  • touch-target-size
    — Minimum 44x44px touch targets
  • hover-vs-tap
    — Use click/tap for primary interactions
  • loading-buttons
    — Disable button during async operations
  • error-feedback
    — Clear error messages near the problem
  • cursor-pointer
    — Add cursor-pointer to clickable elements

Performance (HIGH)

  • image-optimization
    — Use WebP, srcset, lazy loading
  • reduced-motion
    — Check prefers-reduced-motion
  • content-jumping
    — Reserve space for async content

Layout & Responsive (HIGH)

  • viewport-meta
    — width=device-width initial-scale=1
  • readable-font-size
    — Minimum 16px body text on mobile
  • horizontal-scroll
    — Ensure content fits viewport width
  • z-index-management
    — Define z-index scale (10, 20, 30, 50)

Typography & Color (MEDIUM)

  • line-height
    — Use 1.5-1.75 for body text
  • line-length
    — Limit to 65-75 characters per line
  • font-pairing
    — Match heading/body font personalities

Animation (MEDIUM)

  • duration-timing
    — Use 150-300ms for micro-interactions
  • transform-performance
    — Use transform/opacity, not width/height
  • loading-states
    — Skeleton screens or spinners

Style Selection (MEDIUM)

  • style-match
    — Match style to product type
  • consistency
    — Use same style across all pages
  • no-emoji-icons
    — Use SVG icons, not emojis

Charts & Data (LOW)

  • chart-type
    — Match chart type to data type
  • color-guidance
    — Use accessible color palettes
  • data-table
    — Provide table alternative for accessibility

Installation

OpenClaw / Moltbot / Clawbot

npx clawhub@latest install ui-ux-pro-max

Prerequisites

Python 3 is required for the search CLI.

python3 --version

Workflow

When a user requests UI/UX work (design, build, create, implement, review, fix, improve), follow these steps.

Step 1: Analyze Requirements

Extract from the user request:

  • Product type: SaaS, e-commerce, portfolio, dashboard, landing page
  • Style keywords: minimal, playful, professional, elegant, dark mode
  • Industry: healthcare, fintech, gaming, education
  • Stack: React, Vue, Next.js, or default to
    html-tailwind

Step 2: Generate Design System

Always start with

--design-system
to get comprehensive recommendations:

python3 scripts/search.py "<product_type> <industry> <keywords>" --design-system [-p "Project Name"]

This searches 5 domains in parallel (product, style, color, landing, typography), applies reasoning rules from

ui-reasoning.csv
, and returns a complete design system: pattern, style, colors, typography, effects, and anti-patterns.

Example:

python3 scripts/search.py "beauty spa wellness service" --design-system -p "Serenity Spa"

Step 2b: Persist Design System

Save the design system for hierarchical retrieval across sessions:

python3 scripts/search.py "<query>" --design-system --persist -p "Project Name"

Creates:

  • design-system/MASTER.md
    — Global source of truth
  • design-system/pages/
    — Folder for page-specific overrides

With page override:

python3 scripts/search.py "<query>" --design-system --persist -p "Project Name" --page "dashboard"

Hierarchical retrieval: When building a specific page, check

design-system/pages/<page>.md
first. If it exists, its rules override the Master file. Otherwise use
design-system/MASTER.md
exclusively.

Step 3: Supplement with Domain Searches

After generating the design system, use domain searches for additional detail:

python3 scripts/search.py "<keyword>" --domain <domain> [-n <max_results>]
NeedDomainExample
More style options
style
--domain style "glassmorphism dark"
Chart recommendations
chart
--domain chart "real-time dashboard"
UX best practices
ux
--domain ux "animation accessibility"
Alternative fonts
typography
--domain typography "elegant luxury"
Landing structure
landing
--domain landing "hero social-proof"

Step 4: Stack Guidelines

Get implementation-specific best practices. Default to

html-tailwind
if unspecified.

python3 scripts/search.py "<keyword>" --stack html-tailwind

Available stacks:

html-tailwind
,
react
,
nextjs
,
vue
,
svelte
,
swiftui
,
react-native
,
flutter
,
shadcn
,
jetpack-compose


Search Reference

Domains

DomainUse ForExample Keywords
product
Product type recommendationsSaaS, e-commerce, portfolio, healthcare
style
UI styles, colors, effectsglassmorphism, minimalism, dark mode
typography
Font pairings, Google Fontselegant, playful, professional
color
Color palettes by product typesaas, ecommerce, healthcare, fintech
landing
Page structure, CTA strategieshero, testimonial, pricing, social-proof
chart
Chart types, library recstrend, comparison, timeline, funnel
ux
Best practices, anti-patternsanimation, accessibility, z-index
react
React/Next.js performancewaterfall, bundle, suspense, memo
web
Web interface guidelinesaria, focus, keyboard, semantic
prompt
AI prompts, CSS keywords(style name)

Stacks

StackFocus
html-tailwind
Tailwind utilities, responsive, a11y (DEFAULT)
react
State, hooks, performance, patterns
nextjs
SSR, routing, images, API routes
vue
Composition API, Pinia, Vue Router
svelte
Runes, stores, SvelteKit
swiftui
Views, State, Navigation, Animation
react-native
Components, Navigation, Lists
flutter
Widgets, State, Layout, Theming
shadcn
shadcn/ui components, theming, forms
jetpack-compose
Composables, Modifiers, State Hoisting

Output Formats

# ASCII box (default) — best for terminal display
python3 scripts/search.py "fintech crypto" --design-system

# Markdown — best for documentation
python3 scripts/search.py "fintech crypto" --design-system -f markdown

Example Workflow

User request: "Build a landing page for a professional skincare service"

Step 1 — Analyze: Beauty/Spa service, elegant/professional, html-tailwind default.

Step 2 — Design system:

python3 scripts/search.py "beauty spa wellness service elegant" --design-system -p "Serenity Spa"

Step 3 — Supplement:

python3 scripts/search.py "animation accessibility" --domain ux
python3 scripts/search.py "elegant luxury serif" --domain typography

Step 4 — Stack:

python3 scripts/search.py "layout responsive form" --stack html-tailwind

Then synthesize design system + detailed searches and implement.


Search Tips

  1. Be specific — "healthcare SaaS dashboard" beats "app"
  2. Search multiple times — Different keywords reveal different insights
  3. Combine domains — Style + Typography + Color = complete system
  4. Always check UX — Search "animation", "z-index", "accessibility" for common issues
  5. Use the stack flag — Get implementation-specific best practices
  6. Iterate — If first search misses, try different keywords

Common Rules for Professional UI

Icons & Visual Elements

RuleDoDon't
No emoji iconsUse SVG icons (Heroicons, Lucide, Simple Icons)Use emojis as UI icons
Stable hover statesUse color/opacity transitionsUse scale transforms that shift layout
Correct brand logosResearch official SVG from Simple IconsGuess or use incorrect logo paths
Consistent icon sizingFixed viewBox (24x24) with w-6 h-6Mix different icon sizes

Interaction & Cursor

RuleDoDon't
Cursor pointer
cursor-pointer
on all clickable elements
Leave default cursor on interactive elements
Hover feedbackVisual feedback (color, shadow, border)No indication element is interactive
Smooth transitions
transition-colors duration-200
Instant changes or >500ms

Light/Dark Mode Contrast

RuleDoDon't
Glass card (light)
bg-white/80
or higher opacity
bg-white/10
(too transparent)
Text contrast (light)
#0F172A
(slate-900) for text
#94A3B8
(slate-400) for body text
Muted text (light)
#475569
(slate-600) minimum
gray-400 or lighter
Border visibility
border-gray-200
in light mode
border-white/10
(invisible)

Layout & Spacing

RuleDoDon't
Floating navbar
top-4 left-4 right-4
spacing
Stick to
top-0 left-0 right-0
Content paddingAccount for fixed navbar heightLet content hide behind fixed elements
Consistent max-widthSame
max-w-6xl
or
max-w-7xl
Mix different container widths

Pre-Delivery Checklist

Visual Quality

  • No emojis used as icons (use SVG instead)
  • All icons from consistent set (Heroicons/Lucide)
  • Brand logos verified (Simple Icons)
  • Hover states don't cause layout shift
  • Theme colors used directly (
    bg-primary
    not
    var()
    wrapper)

Interaction

  • All clickable elements have
    cursor-pointer
  • Hover states provide clear visual feedback
  • Transitions are 150-300ms
  • Focus states visible for keyboard navigation

Light/Dark Mode

  • Light mode text has 4.5:1 minimum contrast
  • Glass/transparent elements visible in light mode
  • Borders visible in both modes
  • Both modes tested before delivery

Layout

  • Floating elements have proper edge spacing
  • No content hidden behind fixed navbars
  • Responsive at 375px, 768px, 1024px, 1440px
  • No horizontal scroll on mobile

Accessibility

  • All images have alt text
  • Form inputs have labels
  • Color is not the only indicator
  • prefers-reduced-motion
    respected