ui-ux-pro-max
Comprehensive design guide for web, mobile, and desktop applications. Contains 67 styles, 161 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 22 technology stacks. Searchable database with priority-based recommendations.
Prerequisites
The bundled scripts require Python 3 (standard library only — no third-party packages, no network access). Check if it is available:
python3 --version || python --version
If Python is not installed, do not install it yourself. Stop and ask the user to install Python 3 using their preferred method (e.g. from python.org or their OS package manager), then continue once it is available. Never run package-manager or system-modifying commands (sudo, brew, apt, winget, etc.) on the user's machine for this skill.
If the user prefers not to install Python, skip the CLI searches and rely on the Quick Reference sections above.
Note: On Windows, use python instead of python3 to run scripts (e.g., python scripts/search.py instead of python3 scripts/search.py).
How to Use This Skill
Use this skill when the user requests any of the following:
| Scenario |
Trigger Examples |
Start From |
| New project / page |
"做一个 landing page"、"Build a dashboard" |
Step 1 → Step 2 (design system) |
| New component |
"Create a pricing card"、"Add a modal" |
Step 3 (domain search: style, ux) |
| Choose style / color / font |
"What style fits a fintech app?"、"推荐配色" |
Step 2 (design system) |
| Review existing UI |
"Review this page for UX issues"、"检查无障碍" |
Quick Reference checklist above |
| Fix a UI bug |
"Button hover is broken"、"Layout shifts on load" |
Quick Reference → relevant section |
| Improve / optimize |
"Make this faster"、"Improve mobile experience" |
Step 3 (domain search: ux, react) |
| Implement dark mode |
"Add dark mode support" |
Step 3 (domain: style "dark mode") |
| Add charts / data viz |
"Add an analytics dashboard chart" |
Step 3 (domain: chart) |
| Stack best practices |
"React performance tips"、"SwiftUI navigation" |
Step 4 (stack search) |
Follow this workflow:
Step 1: Analyze User Requirements
Extract key information from user request:
- Product type: Entertainment (social, video, music, gaming), Tool (scanner, editor, converter), Productivity (task manager, notes, calendar), or hybrid
- Target audience: C-end consumer users; consider age group, usage context (commute, leisure, work)
- Style keywords: playful, vibrant, minimal, dark mode, content-first, immersive, etc.
- Stack: React Native (this project's only tech stack)
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 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"
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.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 2c: Design Dials (optional)
Three optional 1-10 sliders that tune --design-system output without changing your query. Add any combination of them to the same command:
python3 skills/ui-ux-pro-max/scripts/search.py "<query>" --design-system --variance <1-10> --motion <1-10> --density <1-10>
| Dial |
Low (1-3) |
Mid (4-7) |
High (8-10) |
--variance |
Centered / minimal (biases toward Minimalism-style categories) |
Balanced / modern |
Bold / asymmetric (biases toward Brutalism, Bento Grids) |
--motion |
Subtle micro-interactions |
Standard scroll/stagger motion |
Complex choreography (pin, Flip, SplitText) |
--density |
Spacious (24-96px spacing scale) |
Standard (16-64px, current default) |
Dense/dashboard (8-32px spacing scale) |
--motion attaches a ready-to-use GSAP snippet (with framework notes, Do/Don't, and performance notes) pulled from --domain gsap, matched to the resolved tier (Subtle/Standard/Complex).--density overrides the --space-* CSS variable table in the ASCII/markdown/MASTER.md output — use it for dashboards (high) vs. marketing pages (low) without hand-editing tokens.- Leaving a dial unset keeps that part of the output exactly as it was before (no behavior change).
Example:
python3 skills/ui-ux-pro-max/scripts/search.py "internal analytics dashboard" --design-system --variance 8 --motion 7 --density 8 -p "Ops Console"
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 |
| Product type patterns |
product |
--domain product "entertainment social" |
| More style options |
style |
--domain style "glassmorphism dark" |
| Color palettes |
color |
--domain color "entertainment vibrant" |
| Font pairings |
typography |
--domain typography "playful modern" |
| Chart recommendations |
chart |
--domain chart "real-time dashboard" |
| UX best practices |
ux |
--domain ux "animation accessibility" |
| Landing structure |
landing |
--domain landing "hero social-proof" |
| React Native perf |
react |
--domain react "rerender memo list" |
| App interface a11y |
web |
--domain web "accessibilityLabel touch safe-areas" |
| AI prompt / CSS keywords |
prompt |
--domain prompt "minimalism" |
Step 4: Stack Guidelines
Get implementation-specific best practices for the user's stack:
python3 skills/ui-ux-pro-max/scripts/search.py "<keyword>" --stack <stack>
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 |
gsap |
GSAP animation skeletons by intensity tier |
scroll reveal, stagger, magnetic cursor, page transition |
react |
React/Next.js performance |
waterfall, bundle, suspense, memo, rerender, cache |
web |
App interface guidelines (iOS/Android/React Native) |
accessibilityLabel, touch targets, safe areas, Dynamic Type |
prompt |
AI prompts, CSS keywords |
(style name) |
Available Stacks
| Stack |
Focus |
react-native |
Components, Navigation, Lists |
javafx |
Enterprise desktop apps, AtlantaFX themes, FXML, CSS, Controls, Binding, Threading, Packaging |
JavaFX enterprise examples:
python3 skills/ui-ux-pro-max/scripts/search.py "atlantafx primer enterprise theme" --stack javafx
python3 skills/ui-ux-pro-max/scripts/search.py "enterprise tableview density permission" --stack javafx
Example Workflow
User request: "Make an AI search homepage。"
Step 1: Analyze Requirements
- Product type: Tool (AI search engine)
- Target audience: C-end users looking for fast, intelligent search
- Style keywords: modern, minimal, content-first, dark mode
- Stack: React Native
Step 2: Generate Design System (REQUIRED)
python3 skills/ui-ux-pro-max/scripts/search.py "AI search tool modern minimal" --design-system -p "AI Search"
Output: Complete design system with pattern, style, colors, typography, effects, and anti-patterns.
Step 3: Supplement with Detailed Searches (as needed)
# Get style options for a modern tool product
python3 skills/ui-ux-pro-max/scripts/search.py "minimalism dark mode" --domain style
# Get UX best practices for search interaction and loading
python3 skills/ui-ux-pro-max/scripts/search.py "search loading animation" --domain ux
Step 4: Stack Guidelines
python3 skills/ui-ux-pro-max/scripts/search.py "list performance navigation" --stack react-native
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 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 markdown
Tips for Better Results
Query Strategy
- Use multi-dimensional keywords — combine product + industry + tone + density:
"entertainment social vibrant content-dense" not just "app"
- Try different keywords for the same need:
"playful neon" → "vibrant dark" → "content-first minimal"
- Use
--design-system first for full recommendations, then --domain to deep-dive any dimension you're unsure about
- Add
--stack <stack> for implementation-specific guidance when the target stack is known
Common Sticking Points
| Problem |
What to Do |
| Can't decide on style/color |
Re-run --design-system with different keywords |
| Dark mode contrast issues |
Quick Reference §6: color-dark-mode + color-accessible-pairs |
| Animations feel unnatural |
Quick Reference §7: spring-physics + easing + exit-faster-than-enter |
| Form UX is poor |
Quick Reference §8: inline-validation + error-clarity + focus-management |
| Navigation feels confusing |
Quick Reference §9: nav-hierarchy + bottom-nav-limit + back-behavior |
| Layout breaks on small screens |
Quick Reference §5: mobile-first + breakpoint-consistency |
| Performance / jank |
Quick Reference §3: virtualize-lists + main-thread-budget + debounce-throttle |
Pre-Delivery Checklist
- Run
--domain ux "animation accessibility z-index loading" as a UX validation pass before implementation
- Run through Quick Reference §1–§3 (CRITICAL + HIGH) as a final review
- Test on 375px (small phone) and landscape orientation
- Verify behavior with reduced-motion enabled and Dynamic Type at largest size
- Check dark mode contrast independently (don't assume light mode values work)
- Confirm all touch targets ≥44pt and no content hidden behind safe areas
Common Rules for Professional UI
These are frequently overlooked issues that make UI look unprofessional:
Scope notice: The rules below are for App UI (iOS/Android/React Native/Flutter), not desktop-web interaction patterns.
Icons & Visual Elements
- 默认图标库使用 Phosphor (
@phosphor-icons/react)。src/ui-ux-pro-max/data/icons.csv 中列出的只是常用推荐图标，不是完整集合。
- 当推荐表中找不到合适的图标时：
- 优先继续从 Phosphor 的完整图标集中选择任何语义更贴切的图标；
- 如果 Phosphor 也没有理想选项，可以使用 Heroicons (
@heroicons/react) 作为备选，注意保持风格一致（线性/填充、笔画粗细、圆角风格）。
| Rule |
Standard |
Avoid |
Why It Matters |
| No Emoji as Structural Icons |
Use vector-based icons (e.g., Phosphor @phosphor-icons/react, Heroicons @heroicons/react, react-native-vector-icons, @expo/vector-icons). |
Using emojis (🎨 🚀 ⚙️) for navigation, settings, or system controls. |
Emojis are font-dependent, inconsistent across platforms, and cannot be controlled via design tokens. |
| Vector-Only Assets |
Use SVG or platform vector icons that scale cleanly and support theming. |
Raster PNG icons that blur or pixelate. |
Ensures scalability, crisp rendering, and dark/light mode adaptability. |
| Stable Interaction States |
Use color, opacity, or elevation transitions for press states without changing layout bounds. |
Layout-shifting transforms that move surrounding content or trigger visual jitter. |
Prevents unstable interactions and preserves smooth motion/perceived quality on mobile. |
| Correct Brand Logos |
Use official brand assets and follow their usage guidelines (spacing, color, clear space). |
Guessing logo paths, recoloring unofficially, or modifying proportions. |
Prevents brand misuse and ensures legal/platform compliance. |
| Consistent Icon Sizing |
Define icon sizes as design tokens (e.g., icon-sm, icon-md = 24pt, icon-lg). |
Mixing arbitrary values like 20pt / 24pt / 28pt randomly. |
Maintains rhythm and visual hierarchy across the interface. |
| Stroke Consistency |
Use a consistent stroke width within the same visual layer (e.g., 1.5px or 2px). |
Mixing thick and thin stroke styles arbitrarily. |
Inconsistent strokes reduce perceived polish and cohesion. |
| Filled vs Outline Discipline |
Use one icon style per hierarchy level. |
Mixing filled and outline icons at the same hierarchy level. |
Maintains semantic clarity and stylistic coherence. |
| Touch Target Minimum |
Minimum 44×44pt interactive area (use hitSlop if icon is smaller). |
Small icons without expanded tap area. |
Meets accessibility and platform usability standards. |
| Icon Alignment |
Align icons to text baseline and maintain consistent padding. |
Misaligned icons or inconsistent spacing around them. |
Prevents subtle visual imbalance that reduces perceived quality. |
| Icon Contrast |
Follow WCAG contrast standards: 4.5:1 for small elements, 3:1 minimum for larger UI glyphs. |
Low-contrast icons that blend into the background. |
Ensures accessibility in both light and dark modes. |
Interaction (App)
| Rule |
Do |
Don't |
| Tap feedback |
Provide clear pressed feedback (ripple/opacity/elevation) within 80-150ms |
No visual response on tap |
| Animation timing |
Keep micro-interactions around 150-300ms with platform-native easing |
Instant transitions or slow animations (>500ms) |
| Accessibility focus |
Ensure screen reader focus order matches visual order and labels are descriptive |
Unlabeled controls or confusing focus traversal |
| Disabled state clarity |
Use disabled semantics (disabled/native disabled props), reduced emphasis, and no tap action |
Controls that look tappable but do nothing |
| Touch target minimum |
Keep tap areas >=44x44pt (iOS) or >=48x48dp (Android), expand hit area when icon is smaller |
Tiny tap targets or icon-only hit areas without padding |
| Gesture conflict prevention |
Keep one primary gesture per region and avoid nested tap/drag conflicts |
Overlapping gestures causing accidental actions |
| Semantic native controls |
Prefer native interactive primitives (Button, Pressable, platform equivalents) with proper accessibility roles |
Generic containers used as primary controls without semantics |
Light/Dark Mode Contrast
| Rule |
Do |
Don't |
| Surface readability (light) |
Keep cards/surfaces clearly separated from background with sufficient opacity/elevation |
Overly transparent surfaces that blur hierarchy |
| Text contrast (light) |
Maintain body text contrast >=4.5:1 against light surfaces |
Low-contrast gray body text |
| Text contrast (dark) |
Maintain primary text contrast >=4.5:1 and secondary text >=3:1 on dark surfaces |
Dark mode text that blends into background |
| Border and divider visibility |
Ensure separators are visible in both themes (not just light mode) |
Theme-specific borders disappearing in one mode |
| State contrast parity |
Keep pressed/focused/disabled states equally distinguishable in light and dark themes |
Defining interaction states for one theme only |
| Token-driven theming |
Use semantic color tokens mapped per theme across app surfaces/text/icons |
Hardcoded per-screen hex values |
| Scrim and modal legibility |
Use a modal scrim strong enough to isolate foreground content (typically 40-60% black) |
Weak scrim that leaves background visually competing |
Layout & Spacing
| Rule |
Do |
Don't |
| Safe-area compliance |
Respect top/bottom safe areas for all fixed headers, tab bars, and CTA bars |
Placing fixed UI under notch, status bar, or gesture area |
| System bar clearance |
Add spacing for status/navigation bars and gesture home indicator |
Let tappable content collide with OS chrome |
| Consistent content width |
Keep predictable content width per device class (phone/tablet) |
Mixing arbitrary widths between screens |
| 8dp spacing rhythm |
Use a consistent 4/8dp spacing system for padding/gaps/section spacing |
Random spacing increments with no rhythm |
| Readable text measure |
Keep long-form text readable on large devices (avoid edge-to-edge paragraphs on tablets) |
Full-width long text that hurts readability |
| Section spacing hierarchy |
Define clear vertical rhythm tiers (e.g., 16/24/32/48) by hierarchy |
Similar UI levels with inconsistent spacing |
| Adaptive gutters by breakpoint |
Increase horizontal insets on larger widths and in landscape |
Same narrow gutter on all device sizes/orientations |
| Scroll and fixed element coexistence |
Add bottom/top content insets so lists are not hidden behind fixed bars |
Scroll content obscured by sticky headers/footers |
Pre-Delivery Checklist
Before delivering UI code, verify these items:
Scope notice: This checklist is for App UI (iOS/Android/React Native/Flutter).
Visual Quality
Interaction
Light/Dark Mode
Layout
Accessibility
1---2name: ui-ux-pro-max3description: Comprehensive design guide for web, mobile, and desktop applications. Contains 67 styles, 161 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 22 technology stacks.4---5# ui-ux-pro-max67Comprehensive design guide for web, mobile, and desktop applications. Contains 67 styles, 161 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 22 technology stacks. Searchable database with priority-based recommendations.89# Prerequisites1011The bundled scripts require Python 3 (standard library only — no third-party packages, no network access). Check if it is available:1213```bash14python3 --version || python --version15```1617If Python is not installed, **do not install it yourself**. Stop and ask the user to install Python 3 using their preferred method (e.g. from [python.org](https://www.python.org/downloads/) or their OS package manager), then continue once it is available. Never run package-manager or system-modifying commands (`sudo`, `brew`, `apt`, `winget`, etc.) on the user's machine for this skill.1819If the user prefers not to install Python, skip the CLI searches and rely on the Quick Reference sections above.2021> **Note:** On Windows, use `python` instead of `python3` to run scripts (e.g., `python scripts/search.py` instead of `python3 scripts/search.py`).2223---2425## How to Use This Skill2627Use this skill when the user requests any of the following:2829| Scenario | Trigger Examples | Start From |30|----------|-----------------|------------|31| **New project / page** | "做一个 landing page"、"Build a dashboard" | Step 1 → Step 2 (design system) |32| **New component** | "Create a pricing card"、"Add a modal" | Step 3 (domain search: style, ux) |33| **Choose style / color / font** | "What style fits a fintech app?"、"推荐配色" | Step 2 (design system) |34| **Review existing UI** | "Review this page for UX issues"、"检查无障碍" | Quick Reference checklist above |35| **Fix a UI bug** | "Button hover is broken"、"Layout shifts on load" | Quick Reference → relevant section |36| **Improve / optimize** | "Make this faster"、"Improve mobile experience" | Step 3 (domain search: ux, react) |37| **Implement dark mode** | "Add dark mode support" | Step 3 (domain: style "dark mode") |38| **Add charts / data viz** | "Add an analytics dashboard chart" | Step 3 (domain: chart) |39| **Stack best practices** | "React performance tips"、"SwiftUI navigation" | Step 4 (stack search) |4041Follow this workflow:4243### Step 1: Analyze User Requirements4445Extract key information from user request:46- **Product type**: Entertainment (social, video, music, gaming), Tool (scanner, editor, converter), Productivity (task manager, notes, calendar), or hybrid47- **Target audience**: C-end consumer users; consider age group, usage context (commute, leisure, work)48- **Style keywords**: playful, vibrant, minimal, dark mode, content-first, immersive, etc.49- **Stack**: React Native (this project's only tech stack)5051### Step 2: Generate Design System (REQUIRED)5253**Always start with `--design-system`** to get comprehensive recommendations with reasoning:5455```bash56python3 skills/ui-ux-pro-max/scripts/search.py "<product_type> <industry> <keywords>" --design-system [-p "Project Name"]57```5859This command:601. Searches domains in parallel (product, style, color, landing, typography)612. Applies reasoning rules from `ui-reasoning.csv` to select best matches623. Returns complete design system: pattern, style, colors, typography, effects634. Includes anti-patterns to avoid6465**Example:**66```bash67python3 skills/ui-ux-pro-max/scripts/search.py "beauty spa wellness service" --design-system -p "Serenity Spa"68```6970### Step 2b: Persist Design System (Master + Overrides Pattern)7172To save the design system for **hierarchical retrieval across sessions**, add `--persist`:7374```bash75python3 skills/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persist -p "Project Name"76```7778This creates:79- `design-system/MASTER.md` — Global Source of Truth with all design rules80- `design-system/pages/` — Folder for page-specific overrides8182**With page-specific override:**83```bash84python3 skills/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persist -p "Project Name" --page "dashboard"85```8687This also creates:88- `design-system/pages/dashboard.md` — Page-specific deviations from Master8990**How hierarchical retrieval works:**911. When building a specific page (e.g., "Checkout"), first check `design-system/pages/checkout.md`922. If the page file exists, its rules **override** the Master file933. If not, use `design-system/MASTER.md` exclusively9495**Context-aware retrieval prompt:**96```97I am building the [Page Name] page. Please read design-system/MASTER.md.98Also check if design-system/pages/[page-name].md exists.99If the page file exists, prioritize its rules.100If not, use the Master rules exclusively.101Now, generate the code...102```103104### Step 2c: Design Dials (optional)105106Three optional 1-10 sliders that tune `--design-system` output without changing your query. Add any combination of them to the same command:107108```bash109python3 skills/ui-ux-pro-max/scripts/search.py "<query>" --design-system --variance <1-10> --motion <1-10> --density <1-10>110```111112| Dial | Low (1-3) | Mid (4-7) | High (8-10) |113|------|-----------|-----------|-------------|114| `--variance` | Centered / minimal (biases toward Minimalism-style categories) | Balanced / modern | Bold / asymmetric (biases toward Brutalism, Bento Grids) |115| `--motion` | Subtle micro-interactions | Standard scroll/stagger motion | Complex choreography (pin, Flip, SplitText) |116| `--density` | Spacious (24-96px spacing scale) | Standard (16-64px, current default) | Dense/dashboard (8-32px spacing scale) |117118- `--motion` attaches a ready-to-use GSAP snippet (with framework notes, Do/Don't, and performance notes) pulled from `--domain gsap`, matched to the resolved tier (Subtle/Standard/Complex).119- `--density` overrides the `--space-*` CSS variable table in the ASCII/markdown/MASTER.md output — use it for dashboards (high) vs. marketing pages (low) without hand-editing tokens.120- Leaving a dial unset keeps that part of the output exactly as it was before (no behavior change).121122**Example:**123```bash124python3 skills/ui-ux-pro-max/scripts/search.py "internal analytics dashboard" --design-system --variance 8 --motion 7 --density 8 -p "Ops Console"125```126127### Step 3: Supplement with Detailed Searches (as needed)128129After getting the design system, use domain searches to get additional details:130131```bash132python3 skills/ui-ux-pro-max/scripts/search.py "<keyword>" --domain <domain> [-n <max_results>]133```134135**When to use detailed searches:**136137| Need | Domain | Example |138|------|--------|---------|139| Product type patterns | `product` | `--domain product "entertainment social"` |140| More style options | `style` | `--domain style "glassmorphism dark"` |141| Color palettes | `color` | `--domain color "entertainment vibrant"` |142| Font pairings | `typography` | `--domain typography "playful modern"` |143| Chart recommendations | `chart` | `--domain chart "real-time dashboard"` |144| UX best practices | `ux` | `--domain ux "animation accessibility"` |145| Landing structure | `landing` | `--domain landing "hero social-proof"` |146| React Native perf | `react` | `--domain react "rerender memo list"` |147| App interface a11y | `web` | `--domain web "accessibilityLabel touch safe-areas"` |148| AI prompt / CSS keywords | `prompt` | `--domain prompt "minimalism"` |149150### Step 4: Stack Guidelines151152Get implementation-specific best practices for the user's stack:153154```bash155python3 skills/ui-ux-pro-max/scripts/search.py "<keyword>" --stack <stack>156```157158---159160## Search Reference161162### Available Domains163164| Domain | Use For | Example Keywords |165|--------|---------|------------------|166| `product` | Product type recommendations | SaaS, e-commerce, portfolio, healthcare, beauty, service |167| `style` | UI styles, colors, effects | glassmorphism, minimalism, dark mode, brutalism |168| `typography` | Font pairings, Google Fonts | elegant, playful, professional, modern |169| `color` | Color palettes by product type | saas, ecommerce, healthcare, beauty, fintech, service |170| `landing` | Page structure, CTA strategies | hero, hero-centric, testimonial, pricing, social-proof |171| `chart` | Chart types, library recommendations | trend, comparison, timeline, funnel, pie |172| `ux` | Best practices, anti-patterns | animation, accessibility, z-index, loading |173| `gsap` | GSAP animation skeletons by intensity tier | scroll reveal, stagger, magnetic cursor, page transition |174| `react` | React/Next.js performance | waterfall, bundle, suspense, memo, rerender, cache |175| `web` | App interface guidelines (iOS/Android/React Native) | accessibilityLabel, touch targets, safe areas, Dynamic Type |176| `prompt` | AI prompts, CSS keywords | (style name) |177178### Available Stacks179180| Stack | Focus |181|-------|-------|182| `react-native` | Components, Navigation, Lists |183| `javafx` | Enterprise desktop apps, AtlantaFX themes, FXML, CSS, Controls, Binding, Threading, Packaging |184185**JavaFX enterprise examples:**186187```bash188python3 skills/ui-ux-pro-max/scripts/search.py "atlantafx primer enterprise theme" --stack javafx189python3 skills/ui-ux-pro-max/scripts/search.py "enterprise tableview density permission" --stack javafx190```191192---193194## Example Workflow195196**User request:** "Make an AI search homepage。"197198### Step 1: Analyze Requirements199- Product type: Tool (AI search engine)200- Target audience: C-end users looking for fast, intelligent search201- Style keywords: modern, minimal, content-first, dark mode202- Stack: React Native203204### Step 2: Generate Design System (REQUIRED)205206```bash207python3 skills/ui-ux-pro-max/scripts/search.py "AI search tool modern minimal" --design-system -p "AI Search"208```209210**Output:** Complete design system with pattern, style, colors, typography, effects, and anti-patterns.211212### Step 3: Supplement with Detailed Searches (as needed)213214```bash215# Get style options for a modern tool product216python3 skills/ui-ux-pro-max/scripts/search.py "minimalism dark mode" --domain style217218# Get UX best practices for search interaction and loading219python3 skills/ui-ux-pro-max/scripts/search.py "search loading animation" --domain ux220```221222### Step 4: Stack Guidelines223224```bash225python3 skills/ui-ux-pro-max/scripts/search.py "list performance navigation" --stack react-native226```227228**Then:** Synthesize design system + detailed searches and implement the design.229230---231232## Output Formats233234The `--design-system` flag supports two output formats:235236```bash237# ASCII box (default) - best for terminal display238python3 skills/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system239240# Markdown - best for documentation241python3 skills/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system -f markdown242```243244---245246## Tips for Better Results247248### Query Strategy249250- Use **multi-dimensional keywords** — combine product + industry + tone + density: `"entertainment social vibrant content-dense"` not just `"app"`251- Try different keywords for the same need: `"playful neon"` → `"vibrant dark"` → `"content-first minimal"`252- Use `--design-system` first for full recommendations, then `--domain` to deep-dive any dimension you're unsure about253- Add `--stack <stack>` for implementation-specific guidance when the target stack is known254255### Common Sticking Points256257| Problem | What to Do |258|---------|------------|259| Can't decide on style/color | Re-run `--design-system` with different keywords |260| Dark mode contrast issues | Quick Reference §6: `color-dark-mode` + `color-accessible-pairs` |261| Animations feel unnatural | Quick Reference §7: `spring-physics` + `easing` + `exit-faster-than-enter` |262| Form UX is poor | Quick Reference §8: `inline-validation` + `error-clarity` + `focus-management` |263| Navigation feels confusing | Quick Reference §9: `nav-hierarchy` + `bottom-nav-limit` + `back-behavior` |264| Layout breaks on small screens | Quick Reference §5: `mobile-first` + `breakpoint-consistency` |265| Performance / jank | Quick Reference §3: `virtualize-lists` + `main-thread-budget` + `debounce-throttle` |266267### Pre-Delivery Checklist268269- Run `--domain ux "animation accessibility z-index loading"` as a UX validation pass before implementation270- Run through Quick Reference **§1–§3** (CRITICAL + HIGH) as a final review271- Test on 375px (small phone) and landscape orientation272- Verify behavior with **reduced-motion** enabled and **Dynamic Type** at largest size273- Check dark mode contrast independently (don't assume light mode values work)274- Confirm all touch targets ≥44pt and no content hidden behind safe areas275276---277278## Common Rules for Professional UI279280These are frequently overlooked issues that make UI look unprofessional:281Scope notice: The rules below are for App UI (iOS/Android/React Native/Flutter), not desktop-web interaction patterns.282283### Icons & Visual Elements284285- 默认图标库使用 **Phosphor (`@phosphor-icons/react`)**。`src/ui-ux-pro-max/data/icons.csv` 中列出的只是常用推荐图标，不是完整集合。286- 当推荐表中找不到合适的图标时：287 - **优先继续从 Phosphor 的完整图标集中选择任何语义更贴切的图标**；288 - 如果 Phosphor 也没有理想选项，可以使用 **Heroicons (`@heroicons/react`)** 作为备选，注意保持风格一致（线性/填充、笔画粗细、圆角风格）。289290| Rule | Standard | Avoid | Why It Matters |291|------|----------|--------|----------------|292| **No Emoji as Structural Icons** | Use vector-based icons (e.g., Phosphor `@phosphor-icons/react`, Heroicons `@heroicons/react`, react-native-vector-icons, @expo/vector-icons). | Using emojis (🎨 🚀 ⚙️) for navigation, settings, or system controls. | Emojis are font-dependent, inconsistent across platforms, and cannot be controlled via design tokens. |293| **Vector-Only Assets** | Use SVG or platform vector icons that scale cleanly and support theming. | Raster PNG icons that blur or pixelate. | Ensures scalability, crisp rendering, and dark/light mode adaptability. |294| **Stable Interaction States** | Use color, opacity, or elevation transitions for press states without changing layout bounds. | Layout-shifting transforms that move surrounding content or trigger visual jitter. | Prevents unstable interactions and preserves smooth motion/perceived quality on mobile. |295| **Correct Brand Logos** | Use official brand assets and follow their usage guidelines (spacing, color, clear space). | Guessing logo paths, recoloring unofficially, or modifying proportions. | Prevents brand misuse and ensures legal/platform compliance. |296| **Consistent Icon Sizing** | Define icon sizes as design tokens (e.g., icon-sm, icon-md = 24pt, icon-lg). | Mixing arbitrary values like 20pt / 24pt / 28pt randomly. | Maintains rhythm and visual hierarchy across the interface. |297| **Stroke Consistency** | Use a consistent stroke width within the same visual layer (e.g., 1.5px or 2px). | Mixing thick and thin stroke styles arbitrarily. | Inconsistent strokes reduce perceived polish and cohesion. |298| **Filled vs Outline Discipline** | Use one icon style per hierarchy level. | Mixing filled and outline icons at the same hierarchy level. | Maintains semantic clarity and stylistic coherence. |299| **Touch Target Minimum** | Minimum 44×44pt interactive area (use hitSlop if icon is smaller). | Small icons without expanded tap area. | Meets accessibility and platform usability standards. |300| **Icon Alignment** | Align icons to text baseline and maintain consistent padding. | Misaligned icons or inconsistent spacing around them. | Prevents subtle visual imbalance that reduces perceived quality. |301| **Icon Contrast** | Follow WCAG contrast standards: 4.5:1 for small elements, 3:1 minimum for larger UI glyphs. | Low-contrast icons that blend into the background. | Ensures accessibility in both light and dark modes. |302303304### Interaction (App)305306| Rule | Do | Don't |307|------|----|----- |308| **Tap feedback** | Provide clear pressed feedback (ripple/opacity/elevation) within 80-150ms | No visual response on tap |309| **Animation timing** | Keep micro-interactions around 150-300ms with platform-native easing | Instant transitions or slow animations (>500ms) |310| **Accessibility focus** | Ensure screen reader focus order matches visual order and labels are descriptive | Unlabeled controls or confusing focus traversal |311| **Disabled state clarity** | Use disabled semantics (`disabled`/native disabled props), reduced emphasis, and no tap action | Controls that look tappable but do nothing |312| **Touch target minimum** | Keep tap areas >=44x44pt (iOS) or >=48x48dp (Android), expand hit area when icon is smaller | Tiny tap targets or icon-only hit areas without padding |313| **Gesture conflict prevention** | Keep one primary gesture per region and avoid nested tap/drag conflicts | Overlapping gestures causing accidental actions |314| **Semantic native controls** | Prefer native interactive primitives (`Button`, `Pressable`, platform equivalents) with proper accessibility roles | Generic containers used as primary controls without semantics |315316### Light/Dark Mode Contrast317318| Rule | Do | Don't |319|------|----|----- |320| **Surface readability (light)** | Keep cards/surfaces clearly separated from background with sufficient opacity/elevation | Overly transparent surfaces that blur hierarchy |321| **Text contrast (light)** | Maintain body text contrast >=4.5:1 against light surfaces | Low-contrast gray body text |322| **Text contrast (dark)** | Maintain primary text contrast >=4.5:1 and secondary text >=3:1 on dark surfaces | Dark mode text that blends into background |323| **Border and divider visibility** | Ensure separators are visible in both themes (not just light mode) | Theme-specific borders disappearing in one mode |324| **State contrast parity** | Keep pressed/focused/disabled states equally distinguishable in light and dark themes | Defining interaction states for one theme only |325| **Token-driven theming** | Use semantic color tokens mapped per theme across app surfaces/text/icons | Hardcoded per-screen hex values |326| **Scrim and modal legibility** | Use a modal scrim strong enough to isolate foreground content (typically 40-60% black) | Weak scrim that leaves background visually competing |327328### Layout & Spacing329330| Rule | Do | Don't |331|------|----|----- |332| **Safe-area compliance** | Respect top/bottom safe areas for all fixed headers, tab bars, and CTA bars | Placing fixed UI under notch, status bar, or gesture area |333| **System bar clearance** | Add spacing for status/navigation bars and gesture home indicator | Let tappable content collide with OS chrome |334| **Consistent content width** | Keep predictable content width per device class (phone/tablet) | Mixing arbitrary widths between screens |335| **8dp spacing rhythm** | Use a consistent 4/8dp spacing system for padding/gaps/section spacing | Random spacing increments with no rhythm |336| **Readable text measure** | Keep long-form text readable on large devices (avoid edge-to-edge paragraphs on tablets) | Full-width long text that hurts readability |337| **Section spacing hierarchy** | Define clear vertical rhythm tiers (e.g., 16/24/32/48) by hierarchy | Similar UI levels with inconsistent spacing |338| **Adaptive gutters by breakpoint** | Increase horizontal insets on larger widths and in landscape | Same narrow gutter on all device sizes/orientations |339| **Scroll and fixed element coexistence** | Add bottom/top content insets so lists are not hidden behind fixed bars | Scroll content obscured by sticky headers/footers |340341---342343## Pre-Delivery Checklist344345Before delivering UI code, verify these items:346Scope notice: This checklist is for App UI (iOS/Android/React Native/Flutter).347348### Visual Quality349- [ ] No emojis used as icons (use SVG instead)350- [ ] All icons come from a consistent icon family and style351- [ ] Official brand assets are used with correct proportions and clear space352- [ ] Pressed-state visuals do not shift layout bounds or cause jitter353- [ ] Semantic theme tokens are used consistently (no ad-hoc per-screen hardcoded colors)354355### Interaction356- [ ] All tappable elements provide clear pressed feedback (ripple/opacity/elevation)357- [ ] Touch targets meet minimum size (>=44x44pt iOS, >=48x48dp Android)358- [ ] Micro-interaction timing stays in the 150-300ms range with native-feeling easing359- [ ] Disabled states are visually clear and non-interactive360- [ ] Screen reader focus order matches visual order, and interactive labels are descriptive361- [ ] Gesture regions avoid nested/conflicting interactions (tap/drag/back-swipe conflicts)362363### Light/Dark Mode364- [ ] Primary text contrast >=4.5:1 in both light and dark mode365- [ ] Secondary text contrast >=3:1 in both light and dark mode366- [ ] Dividers/borders and interaction states are distinguishable in both modes367- [ ] Modal/drawer scrim opacity is strong enough to preserve foreground legibility (typically 40-60% black)368- [ ] Both themes are tested before delivery (not inferred from a single theme)369370### Layout371- [ ] Safe areas are respected for headers, tab bars, and bottom CTA bars372- [ ] Scroll content is not hidden behind fixed/sticky bars373- [ ] Verified on small phone, large phone, and tablet (portrait + landscape)374- [ ] Horizontal insets/gutters adapt correctly by device size and orientation375- [ ] 4/8dp spacing rhythm is maintained across component, section, and page levels376- [ ] Long-form text measure remains readable on larger devices (no edge-to-edge paragraphs)377378### Accessibility379- [ ] All meaningful images/icons have accessibility labels380- [ ] Form fields have labels, hints, and clear error messages381- [ ] Color is not the only indicator382- [ ] Reduced motion and dynamic text size are supported without layout breakage383- [ ] Accessibility traits/roles/states (selected, disabled, expanded) are announced correctly
lithStudy