UI UX Pro Max

UI/UX Pro Max - Design Intelligence

Comprehensive design guide for web and mobile applications. Contains 50+ styles, 97 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 9 technology stacks. Searchable database with priority-based recommendations.

When to Apply

Reference these guidelines when:

• 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

1. 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

2. 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 problem
• cursor-pointer - Add cursor-pointer to clickable elements

3. Performance (HIGH)

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

4. 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)

5. 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

6. Animation (MEDIUM)

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

7. 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

8. Charts & Data (LOW)

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

How to Use

Search specific domains using the CLI tool below. Resolve UI_UX_SKILL_DIR to the directory containing the actual loaded SKILL.md before running any example; do not assume the repository working directory. Replace the placeholder with that verified path, never execute it literally:

UI_UX_SKILL_DIR="<resolved-directory-containing-the-loaded-SKILL.md>"
test -f "$UI_UX_SKILL_DIR/scripts/search.py"
python3 -B "$UI_UX_SKILL_DIR/scripts/search.py" --help

-B avoids creating Python bytecode caches in the installed skill directory.

Prerequisites

Check if Python is installed:

python3 --version || python --version

If Python is not installed, install it based on user's OS:

macOS:

brew install python3

Ubuntu/Debian:

sudo apt update && sudo apt install python3

Windows:

winget install Python.Python.3.12

How to Use This Skill

Route by the requested scope before querying:

• New design or explicit redesign: use Step 2 when a design direction needs to be established or replaced. A new page inside an existing design system can reuse that system.
• Existing-page small fix or read-only review: reuse the existing design tokens, components, and stack. Start with the relevant domain query in Step 3; add Step 4 only when stack guidance is needed. Skip design-system generation and persistence. A read-only review reports findings without editing project files.
• Follow repository visual rules and the requested write boundary before generic recommendations. Stop after the requested surface is reviewed or the fix is verified; do not expand into a whole-page redesign.

Step 1: Analyze User Requirements

Extract key information from user request:

• Product type: SaaS, e-commerce, portfolio, dashboard, landing page, etc.
• Style keywords: minimal, playful, professional, elegant, dark mode, etc.
• Industry: healthcare, fintech, gaming, education, etc.
• Stack: use the user-specified or existing project stack; inspect project files when needed. Default to html-tailwind only when neither is established.

Step 2: Generate Design System (New Design or Redesign)

Use --design-system when the selected scope needs a design direction, to get comprehensive recommendations with reasoning:

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

This command:

1. Searches 5 domains in parallel (product, style, color, landing, typography)
2. Applies reasoning rules from ui-reasoning.csv to select best matches
3. Returns complete design system: pattern, style, colors, typography, effects
4. Includes anti-patterns to avoid

Example:

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

Step 2b: Persist Design System (Master + Overrides Pattern)

For design-system work that needs hierarchical retrieval across sessions, optionally add --persist. Omit it for small fixes and read-only reviews:

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

This creates:

• design-system/MASTER.md — Global Source of Truth with all design rules
• design-system/pages/ — Folder for page-specific overrides

With page-specific override:

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

This also creates:

• design-system/pages/dashboard.md — Page-specific deviations from Master

How hierarchical retrieval works:

1. When building a specific page (e.g., "Checkout"), first check design-system/pages/checkout.md
2. If the page file exists, its rules override the Master file
3. If not, use design-system/MASTER.md exclusively

Context-aware retrieval prompt:

I am building the [Page Name] page. Please read design-system/MASTER.md.
Also check if design-system/pages/[page-name].md exists.
If the page file exists, prioritize its rules.
If not, use the Master rules exclusively.
Now, generate the code...

Step 3: Supplement with Detailed Searches (as needed)

For a small fix or read-only review, start with one query relevant to the affected component, such as "keyboard focus button" --domain ux -n 2. For new designs or redesigns, query only the details missing from the design-system result:

python3 -B "$UI_UX_SKILL_DIR/scripts/search.py" "<keyword>" --domain <domain> [-n <max_results>]

When to use detailed searches:

Step 4: Stack Guidelines (Use the Existing Stack)

Get implementation-specific best practices using the user-specified or detected project stack. Use html-tailwind only when no stack is established; replace it in the example below when the project already uses another stack.

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

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

Search Reference

Available Domains

Available Stacks

Example Workflow

This example creates a new design with no established project stack. For an existing-page fix or review, start with the relevant domain search instead.

User request: "Làm landing page cho dịch vụ chăm sóc da chuyên nghiệp"

Step 1: Analyze Requirements

• Product type: Beauty/Spa service
• Style keywords: elegant, professional, soft
• Industry: Beauty/Wellness
• Stack: html-tailwind (no existing stack in this example)

Step 2: Generate Design System (New Design)

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

Output: Complete design system with pattern, style, colors, typography, effects, and anti-patterns.

Step 3: Supplement with Detailed Searches (as needed)

# Get UX guidelines for animation and accessibility
python3 -B "$UI_UX_SKILL_DIR/scripts/search.py" "animation accessibility" --domain ux

# Get alternative typography options if needed
python3 -B "$UI_UX_SKILL_DIR/scripts/search.py" "elegant luxury serif" --domain typography

Step 4: Stack Guidelines

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

Then: Synthesize design system + detailed searches and implement the design.

Output Formats

The --design-system flag supports two output formats:

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

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

Tips for Better Results

1. Be specific with keywords - "healthcare SaaS dashboard" > "app"
2. Search again when needed - Refine keywords only if the first result leaves a relevant gap
3. Combine domains for a new design - Keep small fixes and reviews focused on their relevant domains
4. Check affected UX and accessibility - Use relevant guidance for the requested surface
5. Use stack flag - Get implementation-specific best practices
6. Iterate - If first search doesn't match, try different keywords

Common Rules for Professional UI

These are frequently overlooked issues that make UI look unprofessional:

Icons & Visual Elements

Interaction & Cursor

Light/Dark Mode Contrast

Layout & Spacing

Pre-Delivery Checklist

Apply the relevant items below to the requested surface. For fixes, verify the affected interaction in the running UI, including keyboard/focus and responsive behavior where relevant; query results or code inspection alone do not prove the UI works. For read-only reviews, report findings with available evidence and label missing runtime checks UNVERIFIED. Do not widen a small fix into a full-site audit.

Visual Quality

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

Interaction

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

Light/Dark Mode

• Light mode text has sufficient contrast (4.5:1 minimum)
• Glass/transparent elements visible in light mode
• Borders visible in both modes
• Test both modes before delivery

Layout

• Floating elements have proper spacing from edges
• 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