| name | ui-ux-pro-max |
| description | UI/UX design intelligence. 67 styles, 96 palettes, 57 font pairings, 25 charts, 13 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Ethics: 30 Laws of UX, 7 Humane by Design principles, 16 deceptive design patterns to avoid. Use this skill for ethical design audits, dark pattern detection, humane product reviews, and any time someone asks about Laws of UX, dark patterns, deceptive design, or humane technology. Integrations: shadcn/ui MCP for component search and examples. Design foundations: 7 Elements of Design (line, shape, form, texture, space, color, value), 12 Principles of Animation (Disney). Topics: elements of design, principles of animation, motion design, visual hierarchy, composition, negative space, easing, timing, squash and stretch. |
UI/UX Pro Max - Design Intelligence
Comprehensive design guide for web and mobile applications. Contains 67 styles, 96 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 13 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
Automated Code Audit (run this first for any review task)
scripts/audit.py scans real code files and returns severity-ranked findings with file:line references. It replaces manual checklist reading — the model's job is to interpret output and fix issues, not to mentally check 56 reference files.
python skills/ui-ux-pro-max/scripts/audit.py src/checkout.tsx
python skills/ui-ux-pro-max/scripts/audit.py src/
python skills/ui-ux-pro-max/scripts/audit.py src/ --focus deceptive
python skills/ui-ux-pro-max/scripts/audit.py src/ --focus accessibility
python skills/ui-ux-pro-max/scripts/audit.py src/ --focus humane
python skills/ui-ux-pro-max/scripts/audit.py src/ --severity critical high
python skills/ui-ux-pro-max/scripts/audit.py src/ --summary
python skills/ui-ux-pro-max/scripts/audit.py src/ --format json
Exit code 1 if any critical findings — safe to use in CI pre-commit hooks.
--summary flag: Groups findings by violation ID instead of per-file detail. Shows top 15 violation types ranked by frequency, and top 10 files by issue count. Use this when scanning large directories — scan first with --summary, then drill into specific violations with regular output.
When to run:
- Any code review, audit, or "check this" request → run audit.py on the files first
- Before delivering UI code → run on all modified files
- When user mentions accessibility, dark patterns, or ethical design → run audit.py, then ethics_check.py
Workflow:
- Run
audit.py → read the output → fix critical/high issues in the actual files
- For deep guidance on a specific finding, read the
Ref: path listed in the finding
- Reference files are only needed when explaining WHY a finding matters or generating compliant code examples
Ethics & Principles Resources
Three reference frameworks in references/. Read index for overview; individual files for deep guidance on a specific finding.
| Resource | Index | Individual Files |
|---|
| Laws of UX | references/laws-index.md | references/laws/<name>.md — 30 files |
| Humane by Design | references/humane-index.md | references/humane/<name>.md — 7 files |
| Deceptive Design | references/deceptive-index.md | references/deceptive/<name>.md — 16 files |
Each individual file contains: summary, code review flags, regulatory context, compliant implementation, metrics.
Design Foundations
Two foundational reference libraries for visual design and motion:
| Resource | File | Contents |
|---|
| Elements of Design | references/elements-of-design.md | 7 visual elements — line, shape, form, texture, space, color, value — with UI code examples |
| Principles of Animation | references/principles-of-animation.md | Disney's 12 principles applied to UI motion — easing, timing, squash, anticipation, staging |
When to read:
- Designing a new UI from scratch → read
elements-of-design.md before choosing styles
- Implementing any animation → read
principles-of-animation.md for timing/easing guidance
- Design review mentions "feels flat", "looks cheap", "animation feels wrong" → both files
- User asks about composition, visual hierarchy, motion design, or animation principles → reference these
Ethics Checker — feature-level keyword lookup
Use ethics_check.py when you have a feature description (not code) and need to know which laws/principles/patterns are relevant before designing:
python skills/ui-ux-pro-max/scripts/ethics_check.py "checkout flow with subscription upsell"
python skills/ui-ux-pro-max/scripts/ethics_check.py "notification settings" --focus humane
python skills/ui-ux-pro-max/scripts/ethics_check.py "pricing page" --focus deceptive
python skills/ui-ux-pro-max/scripts/ethics_check.py "form design" --focus laws
python skills/ui-ux-pro-max/scripts/ethics_check.py --audit-all
When to use:
- Early design phase (before code exists) → ethics_check.py
- Reviewing existing code → audit.py (faster, file:line findings)
- Comprehensive pre-launch ethics review →
--audit-all
Rule Categories by Priority
| Priority | Category | Impact | Domain |
|---|
| 1 | Accessibility | CRITICAL | ux |
| 2 | Touch & Interaction | CRITICAL | ux |
| 3 | Performance | HIGH | ux |
| 4 | Layout & Responsive | HIGH | ux |
| 5 | Typography & Color | MEDIUM | typography, color |
| 6 | Animation | MEDIUM | ux |
| 7 | Style Selection | MEDIUM | style, product |
| 8 | Charts & Data | LOW | chart |
| 9 | Elements of Design | MEDIUM | design |
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 - 100ms (tap), 150ms (tooltip), 200ms (fade/page), 300ms (modal/drawer)
transform-performance - Use transform/opacity, not width/height/top/left
loading-states - Skeleton screens or spinners; skeleton matches final layout shape
easing - ease-out for enter, ease-in for exit, never linear for UI elements
spring-physics - Use spring for scale/transform (natural feel); duration+easing for opacity
principles - See references/principles-of-animation.md for Disney's 12 principles applied to UI
Principles quick-ref:
- Slow In/Out:
cubic-bezier(0.25, 0, 0, 1) enter · cubic-bezier(0.3, 0, 1, 0.3) exit
- Squash/Stretch:
whileTap: {scale: 0.97} · spring overshoot: type: 'spring', stiffness: 300
- Anticipation: hover state (−2px lift) before click; loading pulse before skeleton appears
- Staging: stagger children
50ms · hero enters first, supporting content follows
- Follow Through: exit last item last · momentum continues 1 tick past stop
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.
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
When user requests UI/UX work (design, build, create, implement, review, fix, improve), follow this workflow:
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: React, Vue, Next.js, or default to
html-tailwind
Check for existing design system first: If DESIGN.md exists in the project root, read it before doing anything else. It is the single source of truth — use it instead of generating a new design system. Only run search.py --design-system if no DESIGN.md exists.
Step 2: Generate Design System (REQUIRED if no DESIGN.md exists)
Always start with --design-system to get comprehensive recommendations with reasoning:
python3 skills/ui-ux-pro-max/scripts/search.py "<product_type> <industry> <keywords>" --design-system [-p "Project Name"]
This command:
- Searches 5 domains in parallel (product, style, color, landing, typography)
- Applies reasoning rules from
ui-reasoning.csv to select best matches
- Returns complete design system: pattern, style, colors, typography, effects
- Includes anti-patterns to avoid
Example:
python3 skills/ui-ux-pro-max/scripts/search.py "beauty spa wellness service" --design-system -p "Serenity Spa"
Multiple alternatives — when the first recommendation might not fit, request N options ranked by match score:
python3 skills/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system --alternatives 3
Each option shows as a separate block with OPTION 1 / 2 / 3 header. Use the first option by default; show alternatives when the user is deciding between directions. --persist always writes option 1.
Step 2b: Persist Design System (DESIGN.md in Project Root)
To write the design system as a persistent file, add --persist:
python3 skills/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persist -p "Project Name"
This writes:
DESIGN.md — single source of truth, placed directly in the project root
With page-specific override:
python3 skills/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persist -p "Project Name" --page "checkout"
This also writes:
DESIGN-checkout.md — page-specific overrides alongside DESIGN.md
How to use DESIGN.md:
- Read
DESIGN.md before writing any component — treat every decision as a constraint
- If a page override exists (
DESIGN-checkout.md), its rules take precedence for that page
- If the user asks to "make it pop" or "add personality", interpret within the design system — don't override it
See references/design-template.md for the full 9-section structure and template.
Step 3: Supplement with Detailed Searches (as needed)
After getting the design system, use domain searches to get additional details:
python3 skills/ui-ux-pro-max/scripts/search.py "<keyword>" --domain <domain> [-n <max_results>]
When to use detailed searches:
| Need | Domain | Example |
|---|
| 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 (Default: html-tailwind)
Get implementation-specific best practices. If user doesn't specify a stack, default to html-tailwind.
python3 skills/ui-ux-pro-max/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
| Domain | Use For | Example Keywords |
|---|
product | Product type recommendations | SaaS, e-commerce, portfolio, healthcare, beauty, service |
style | UI styles, colors, effects | glassmorphism, minimalism, dark mode, brutalism |
typography | Font pairings, Google Fonts | elegant, playful, professional, modern |
color | Color palettes by product type | saas, ecommerce, healthcare, beauty, fintech, service |
landing | Page structure, CTA strategies | hero, hero-centric, testimonial, pricing, social-proof |
chart | Chart types, library recommendations | trend, comparison, timeline, funnel, pie |
ux | Best practices, anti-patterns | animation, accessibility, z-index, loading |
react | React/Next.js performance patterns | waterfall, bundle, suspense, memo, rerender, cache |
web | Web interface guidelines | aria, focus, keyboard, semantic, virtualize |
icons | Icon name lookup (Lucide) | menu, arrow, search, chevron, user, settings |
prompt | AI prompt + CSS keywords for a style | (style name, e.g. "glassmorphism") |
animation | Motion patterns: enter/exit/hover/loading/feedback | fade, slide, spring, stagger, skeleton, progress |
components | Component library picker (18 libraries) | headless, accessible, shadcn, react, vue, svelte, tailwind |
Available Stacks
| Stack | Focus |
|---|
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, patterns |
astro | Astro islands, content collections, SSG patterns |
nuxtjs | Nuxt 3, composables, auto-imports, Pinia |
nuxt-ui | Nuxt UI components, theming, Tailwind integration |
jetpack-compose | Composables, Modifiers, State Hoisting, Recomposition |
Example Workflow
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 (default)
Step 2: Generate Design System (REQUIRED)
python3 skills/ui-ux-pro-max/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)
python3 skills/ui-ux-pro-max/scripts/search.py "animation accessibility" --domain ux
python3 skills/ui-ux-pro-max/scripts/search.py "elegant luxury serif" --domain typography
Step 4: Stack Guidelines
python3 skills/ui-ux-pro-max/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:
python3 skills/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system
python3 skills/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system -f markdown
Tips for Better Results
- Be specific with keywords - "healthcare SaaS dashboard" > "app"
- Search multiple times - Different keywords reveal different insights
- Combine domains - Style + Typography + Color = Complete design system
- Always check UX - Search "animation", "z-index", "accessibility" for common issues
- Use stack flag - Get implementation-specific best practices
- 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
| Rule | Do | Don't |
|---|
| No emoji icons | Use SVG icons (Heroicons, Lucide, Simple Icons) | Use emojis like 🎨 🚀 ⚙️ as UI icons |
| Stable hover states | Use color/opacity transitions on hover | Use scale transforms that shift layout |
| Correct brand logos | Research official SVG from Simple Icons | Guess or use incorrect logo paths |
| Consistent icon sizing | Use fixed viewBox (24x24) with w-6 h-6 | Mix different icon sizes randomly |
Interaction & Cursor
| Rule | Do | Don't |
|---|
| Cursor pointer | Add cursor-pointer to all clickable/hoverable cards | Leave default cursor on interactive elements |
| Hover feedback | Provide visual feedback (color, shadow, border) | No indication element is interactive |
| Smooth transitions | Use transition-colors duration-200 | Instant state changes or too slow (>500ms) |
Light/Dark Mode Contrast
| Rule | Do | Don't |
|---|
| Glass card light mode | Use bg-white/80 or higher opacity | Use bg-white/10 (too transparent) |
| Text contrast light | Use #0F172A (slate-900) for text | Use #94A3B8 (slate-400) for body text |
| Muted text light | Use #475569 (slate-600) minimum | Use gray-400 or lighter |
| Border visibility | Use border-gray-200 in light mode | Use border-white/10 (invisible) |
Layout & Spacing
| Rule | Do | Don't |
|---|
| Floating navbar | Add top-4 left-4 right-4 spacing | Stick navbar to top-0 left-0 right-0 |
| Content padding | Account for fixed navbar height | Let content hide behind fixed elements |
| Consistent max-width | Use same max-w-6xl or max-w-7xl | Mix different container widths |
Additional Scripts
contrast.py — WCAG Contrast Checker
Computes actual contrast ratios using the WCAG relative luminance formula. Fills the gap audit.py cannot cover (CSS variables → actual hex values aren't resolved at parse time).
python skills/ui-ux-pro-max/scripts/contrast.py "#64748B" "#FFFFFF"
python skills/ui-ux-pro-max/scripts/contrast.py DESIGN.md
python skills/ui-ux-pro-max/scripts/contrast.py --list "#0F172A" "#64748B" "#FFFFFF" "#F8FAFC"
Output: ratio, AA/AAA pass/fail for normal and large text. Exit code 1 if any AA failure. Run against DESIGN.md whenever you define or modify the color palette.
generate_css_vars.py — Design Token Extractor
Converts DESIGN.md color/typography/spacing decisions into CSS custom properties (:root {}) and optionally a Tailwind extend config.
python skills/ui-ux-pro-max/scripts/generate_css_vars.py DESIGN.md
python skills/ui-ux-pro-max/scripts/generate_css_vars.py DESIGN.md --out design-tokens.css
python skills/ui-ux-pro-max/scripts/generate_css_vars.py DESIGN.md --tailwind
Token workflow: --design-system --persist → generate_css_vars.py → import tokens into project → validate_tokens.py enforces compliance.
validate_tokens.py — Off-System Hex Detector
Scans source files for hex color values not defined in the design system. Catches hardcoded colors that bypass the token system.
python skills/ui-ux-pro-max/scripts/validate_tokens.py DESIGN.md src/
python skills/ui-ux-pro-max/scripts/validate_tokens.py design-tokens.css src/
Output: file:line: #hex not in design system. Exit code 1 if violations found. Run before delivery on all modified UI files.
post_write_audit.py — Automatic Audit Hook
Runs audit.py --severity critical high automatically every time Claude writes a UI file. Prints findings immediately so they're caught during generation rather than after.
Setup — add to .claude/settings.json in the project root:
{
"hooks": {
"PostToolUse": [{
"matcher": "Write",
"hooks": [{
"type": "command",
"command": "python /ABSOLUTE/PATH/TO/skills/ui-ux-pro-max/scripts/post_write_audit.py"
}]
}]
}
}
Replace /ABSOLUTE/PATH/TO/ with the actual path to the skill on this machine. The hook reads the Write tool payload from stdin — no arguments needed. Only triggers on .tsx, .jsx, .ts, .js, .vue, .svelte, .css, .html files; silently skips all other file types.
Pre-Delivery Checklist
Before delivering UI code, verify these items:
Visual Quality
Interaction
Light/Dark Mode
Layout
Accessibility
Ethics & Accessibility (automated — run audit.py on all modified files)
python skills/ui-ux-pro-max/scripts/audit.py <file_or_directory>
python skills/ui-ux-pro-max/scripts/audit.py <file_or_directory> --severity critical high
python skills/ui-ux-pro-max/scripts/ethics_check.py "<feature description>"
- Zero critical findings required before delivery
- Read the
Ref: path on any finding for compliant implementation examples
What audit.py cannot detect (check manually):
- Visual contrast ratios from CSS variables or Tailwind tokens (can't resolve to actual hex values)
- Missing loading / empty / error states (can't detect absence of code)
- Screen reader reading order and announcement logic
- Server-side countdown validation (fake urgency check is client-only)
- Fake social proof in content strings
role + aria-* completeness on fully custom components