UI/UX Quality System

/ui-ux-pro-max

Comprehensive design intelligence for web and mobile applications: 50+ styles, 97 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 9 technology stacks, with priority-based recommendations. The user pastes code, describes the product, or uploads what they have; deliver a concrete design system plus implementation guidance or fixed code as chat artifacts.

When to Apply

• Designing new UI components or pages
• Choosing color palettes and typography
• Reviewing pasted code for UX issues
• Building landing pages or dashboards (for premium marketing-page aesthetics, use premium-web-design)
• 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

The Knowledge Base

This skill ships a searchable database under its own directory:

• data/*.csv - domain databases: styles.csv, colors.csv, typography.csv, products.csv, landing.csv, charts.csv, ux-guidelines.csv, ui-reasoning.csv, react-performance.csv, web-interface.csv, icons.csv, prompts.csv
• data/stacks/*.csv - per-stack implementation guidelines: html-tailwind, react, nextjs, vue, svelte, swiftui, react-native, flutter, shadcn
• scripts/search.py - optional CLI (--design-system, --domain <domain>, --stack <stack>) when a Python runtime is available

When a runtime is available, prefer the CLI:

python3 scripts/search.py "<product_type> <industry> <keywords>" --design-system [-p "Project Name"]
python3 scripts/search.py "<keyword>" --domain <domain> [-n <max_results>]
python3 scripts/search.py "<keyword>" --stack html-tailwind

Otherwise read the relevant CSV files directly and apply the same reasoning: match product type, style, colors, typography, and effects, and note the anti-patterns to avoid.

Workflow

When the user requests UI/UX work (design, build, create, implement, review, fix, improve):

Step 1: Analyze Requirements

Extract from the 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: React, Vue, Next.js, or default to html-tailwind

Step 2: Generate a Design System (REQUIRED)

Always start with a complete design-system recommendation before writing any UI code: pattern, style, colors (hex), typography (specific pairings), effects, and anti-patterns to avoid. Source it from the product, style, color, landing, and typography domains and the reasoning rules in ui-reasoning.csv. Present it to the user as a compact summary before or alongside implementation.

Step 3: Supplement with Detailed Lookups (as needed)

Step 4: Apply Stack Guidelines

Default to html-tailwind if the user does not specify a stack. Pull the matching data/stacks/*.csv guidance and follow it in the delivered code.

Example. User asks: "Make a landing page for a professional skincare service." Analyze (beauty/wellness, elegant, html-tailwind default), generate the design system (pattern, style, palette, typography, effects, anti-patterns), supplement with ux and typography lookups, then implement and deliver the code artifact.

Common Rules for Professional UI

Frequently overlooked issues that make UI look unprofessional:

Icons & Visual Elements

Interaction & Cursor

Light/Dark Mode Contrast

Layout & Spacing

Pre-Delivery Checklist

Before delivering UI code, verify:

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

Tips for Better Results

1. Be specific with keywords - "healthcare SaaS dashboard" beats "app"
2. Search multiple times - Different keywords reveal different insights
3. Combine domains - Style + Typography + Color = complete design system
4. Always check UX - Look up "animation", "z-index", "accessibility" for common issues
5. Use stack guidance - Get implementation-specific best practices
6. Iterate - If the first lookup doesn't match, try different keywords

Usage

/ui-ux-pro-max $ARGUMENTS