UI / UX

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

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 "  " --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 "" --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 "" --design-system --persist -p "Project Name" --page "dashboard"

Hierarchical retrieval: When building a specific page, check design-system/pages/.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 "" --domain  [-n ]

Step 4: Stack Guidelines

Get implementation-specific best practices. Default to html-tailwind if unspecified.

python3 scripts/search.py "" --stack html-tailwind

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

---

Search Reference

Domains

Stacks

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

Interaction & Cursor

Light/Dark Mode Contrast

Layout & Spacing

---

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