Imported from aarushlohit/TheRocketProject (
rocket/external/shokunin/.pack/skills/ui-ux-pro-max/SKILL.md). Install upstream withnpx skills add aarushlohit/TheRocketProject --skill ui-ux-pro-max. Copyright stays with the author (MIT).
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
Workflow
- Analyze requirements — extract product type, style keywords, industry, and technology stack from user request. Default to
html-tailwindif no stack specified. - Generate design system — run
python3 scripts/search.py "<query>" --design-system -p "Project Name"for comprehensive style, color, typography, and effects recommendations. - Supplement with domain searches — query
style,typography,ux,chart, orlandingdomains for additional detail on specific areas. - Persist design system for multi-page projects — use
--persistto createdesign-system/MASTER.mdwith page-specific overrides via--page. - Apply stack guidelines — run
--stack <stack>(default: html-tailwind) for implementation-specific best practices. - Implement with the design system as source of truth — colors, typography, spacing, and effects all come from the persisted MASTER.md.
- Run pre-delivery checklist — verify visual quality, interaction, light/dark mode, layout, and accessibility before delivering code.
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 |
Quick Reference
1. Accessibility (CRITICAL)
color-contrast- Minimum 4.5:1 ratio for normal textfocus-states- Visible focus rings on interactive elementsalt-text- Descriptive alt text for meaningful imagesaria-labels- aria-label for icon-only buttonskeyboard-nav- Tab order matches visual orderform-labels- Use label with for attribute
2. Touch & Interaction (CRITICAL)
touch-target-size- Minimum 44x44px touch targetshover-vs-tap- Use click/tap for primary interactionsloading-buttons- Disable button during async operationserror-feedback- Clear error messages near problemcursor-pointer- Add cursor-pointer to clickable elements
3. Performance (HIGH)
image-optimization- Use WebP, srcset, lazy loadingreduced-motion- Check prefers-reduced-motioncontent-jumping- Reserve space for async content
4. Layout & Responsive (HIGH)
viewport-meta- width=device-width initial-scale=1readable-font-size- Minimum 16px body text on mobilehorizontal-scroll- Ensure content fits viewport widthz-index-management- Define z-index scale (10, 20, 30, 50)
5. Typography & Color (MEDIUM)
line-height- Use 1.5-1.75 for body textline-length- Limit to 65-75 characters per linefont-pairing- Match heading/body font personalities
6. Animation (MEDIUM)
duration-timing- Use 150-300ms for micro-interactionstransform-performance- Use transform/opacity, not width/heightloading-states- Skeleton screens or spinners
7. Style Selection (MEDIUM)
style-match- Match style to product typeconsistency- Use same style across all pagesno-emoji-icons- Use SVG icons, not emojis
8. Charts & Data (LOW)
chart-type- Match chart type to data typecolor-guidance- Use accessible color palettesdata-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 --versionIf Python is not installed, install it based on user's OS:
macOS:
brew install python3Ubuntu/Debian:
sudo apt update && sudo apt install python3Windows:
winget install Python.Python.3.12How 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
Step 2: Generate Design System (REQUIRED)
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.csvto 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"Step 2b: Persist Design System (Master + Overrides Pattern)
To save the design system for hierarchical retrieval across sessions, add --persist:
python3 skills/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persist -p "Project Name"This creates:
design-system/MASTER.md— Global Source of Truth with all design rulesdesign-system/pages/— Folder for page-specific overrides
With page-specific override:
python3 skills/ui-ux-pro-max/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:
- When building a specific page (e.g., "Checkout"), first check
design-system/pages/checkout.md - If the page file exists, its rules override the Master file
- If not, use
design-system/MASTER.mdexclusively
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-tailwindAvailable 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 | waterfall, bundle, suspense, memo, rerender, cache |
web |
Web interface guidelines | aria, focus, keyboard, semantic, virtualize |
prompt |
AI prompts, CSS keywords | (style name) |
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 |
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)
# Get UX guidelines for animation and accessibility
python3 skills/ui-ux-pro-max/scripts/search.py "animation accessibility" --domain ux
# Get alternative typography options if needed
python3 skills/ui-ux-pro-max/scripts/search.py "elegant luxury serif" --domain typographyStep 4: Stack Guidelines
python3 skills/ui-ux-pro-max/scripts/search.py "layout responsive form" --stack html-tailwindThen: 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 skills/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system
# Markdown - best for documentation
python3 skills/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system -f markdownTips 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 |
Pre-Delivery Checklist
Before delivering UI code, verify these items:
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-motionrespected
Error Handling
| Cause | Fix |
|---|---|
| Python not installed, search script fails | Run python3 --version first. Install per OS instructions in Prerequisites section. |
--design-system returns no matching style |
Re-run with different keywords. Try broader terms or synonyms. |
--persist fails due to permissions |
Verify write access to project root. Run from a directory with write permissions. |
--stack flag returns no results for chosen stack |
Verify the stack name matches exactly (use html-tailwind not "tailwind"). Check available stacks list. |
--domain search returns empty results |
Broaden keywords. Check domain name matches the available domains table. |
| Merged output has conflicting design rules | Review MASTER.md for contradictions. Default to the first matching rule in hierarchy. |
| Page-specific override file not found | Use --page "pagename" flag to regenerate. File is created at design-system/pages/. |
| Gradient/text color contrast fails WCAG 2.1 | Check color-contrast ratio. Minimum 4.5:1 for normal text, 3:1 for large text. |
Anti-Patterns
| Pattern | Problem | Fix |
|---|---|---|
| Emojis used as UI icons | Looks unprofessional, inconsistent sizing | Use SVG icons from Lucide, Heroicons, or Phosphor exclusively |
Scale transforms on hover without cursor-pointer |
No indication element is interactive | Add cursor-pointer to all clickable/hoverable elements |
h-screen on mobile layouts |
iOS Safari viewport bugs cause layout shift | Always use min-h-[100dvh] instead |
Transparent glass cards in light mode (bg-white/10) |
Invisible, illegible on white backgrounds | Use bg-white/80 or higher opacity in light mode |
Missing prefers-reduced-motion media query |
Animations cause discomfort for users with motion sensitivity | Gate every animation behind @media (prefers-reduced-motion: reduce) |
Floating navbar flush to viewport edges (top-0 left-0) |
Content hides behind navigation | Add top-4 left-4 right-4 spacing on floating navbars |
| Mixing different icon libraries on one page | Inconsistent stroke width, sizing, and visual weight | Pick one icon set for the entire project |
| Tailing gray-400-level text for body copy in light mode | Fails WCAG contrast minimums | Use slate-600 (#475569) minimum for body text in light mode |
Sources
- WCAG 2.1/2.2 — Web Content Accessibility Guidelines (w3.org/WAI)
- Nielsen Norman Group — "UX Guidelines for Ecommerce" (nngroup.com)
- shadcn/ui — Component library and theming (ui.shadcn.com)
- Tailwind CSS — Utility-first framework (tailwindcss.com)
- Google Fonts — Typography pairs and metrics (fonts.google.com)
- Refactoring UI — Adam Wathan & Steve Schoger (refactoringui.com)
- Practical UI — Adham Dannaway (practical-ui.com)
- Erik Kennedy — "7 Rules for Creating Gorgeous UI" (learnui.design)
- OKLCH Color Picker — oklch.com
- Adam Argyle — "Building a Color Scheme" (web.dev)
Checklist
- Skill loads without errors in the AI agent
- YAML frontmatter is valid (description, compatibility, audience)
- Workflow section provides clear step-by-step instructions
- Error handling section covers common failure modes
- All referenced files (references/, scripts/, assets/) exist
- Skill triggers correctly for intended use cases
- No broken links or missing resources