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.
⚠️ TREIDO PROJECT: This project uses Tailwind v4 with CSS variables.
Use h-(--spacing-touch-md) NOT h-11 or min-h-[44px].
See globals.css for all design tokens.
Treido note: Focus on Next.js + Tailwind v4 + shadcn/ui. Ignore non-relevant stack sections unless explicitly asked.
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
| 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
🎯 TREIDO PROJECT: Tailwind v4 Token Syntax
This project uses Tailwind v4 with CSS variables. Do NOT use arbitrary values or v3 syntax.
Touch Target Tokens
/* globals.css defines these tokens */
--spacing-touch-xs: 2rem; /* 32px - minimum WCAG */
--spacing-touch-sm: 2.25rem; /* 36px - compact */
--spacing-touch: 2.5rem; /* 40px - default */
--spacing-touch-md: 2.75rem; /* 44px - Apple minimum */
--spacing-touch-lg: 3rem; /* 48px - bottom nav */
Correct Syntax
// ❌ WRONG - Arbitrary values (v3 style)
className="min-h-[44px] min-w-[44px]"
className="h-11" // Magic number
// ✅ CORRECT - Tailwind v4 CSS variable syntax
className="min-h-(--spacing-touch-md) min-w-(--spacing-touch-md)"
className="h-(--spacing-touch-md)"
// ✅ CORRECT - Using size for square touch targets
className="size-(--spacing-touch-md)"
Common Treido Patterns
| Use Case |
Token |
Tailwind v4 Class |
| Bottom nav items |
48px |
h-(--spacing-touch-lg) |
| Header icons |
44px |
size-(--spacing-touch-md) |
| Button height |
44px |
h-(--spacing-button) |
| Compact button |
36px |
h-(--spacing-button-sm) |
| Input height |
44px |
h-(--spacing-input) |
| Category pills |
40px |
h-(--spacing-touch) |
Full Example
// Touch-friendly button with Treido tokens
<button
className="
min-h-(--spacing-touch-md)
px-4
rounded-lg
bg-primary
text-primary-foreground
active:opacity-80
transition-opacity
"
>
Tap me
</button>
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 --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
Step 2: Generate Design System (REQUIRED)
Always start with --design-system to get comprehensive recommendations with reasoning:
python3 .codex/skills/treido-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 .codex/skills/treido-ui-ux-pro-max/scripts/search.py "beauty spa wellness service" --design-system -p "Serenity Spa"
Step 3: Supplement with Detailed Searches (as needed)
After getting the design system, use domain searches to get additional details:
python3 .codex/skills/treido-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 .codex/skills/treido-ui-ux-pro-max/scripts/search.py "<keyword>" --stack html-tailwind
Available stacks: html-tailwind, react, nextjs, vue, svelte, swiftui, react-native, flutter, shadcn
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 |
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 .codex/skills/treido-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 .codex/skills/treido-ui-ux-pro-max/scripts/search.py "animation accessibility" --domain ux
# Get alternative typography options if needed
python3 .codex/skills/treido-ui-ux-pro-max/scripts/search.py "elegant luxury serif" --domain typography
Step 4: Stack Guidelines
python3 .codex/skills/treido-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:
# ASCII box (default) - best for terminal display
python3 .codex/skills/treido-ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system
# Markdown - best for documentation
python3 .codex/skills/treido-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-card or bg-surface tokens |
Use bg-white/80 (opacity modifier) |
| Text contrast light |
Use text-foreground token |
Use hardcoded hex like #0F172A |
| Muted text light |
Use text-muted-foreground token |
Use palette colors like gray-400 |
| Border visibility |
Use border-border token |
Use palette like border-gray-200 |
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
Interaction
Light/Dark Mode
Layout
Accessibility
1---2name: treido-ui-ux-pro-max3description: UI/UX design intelligence tuned for Treido (Next.js + shadcn/ui + Tailwind v4 tokens). Use for high-polish UI specs, layout/typography/interaction review, and “native app feel” guidance.4---5
6# UI/UX Pro Max - Design Intelligence
7
8Comprehensive 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.
9
10> **⚠️ TREIDO PROJECT:** This project uses **Tailwind v4** with CSS variables.
11> Use `h-(--spacing-touch-md)` NOT `h-11` or `min-h-[44px]`.
12> See [globals.css](app/globals.css) for all design tokens.
13
14> **Treido note**: Focus on **Next.js + Tailwind v4 + shadcn/ui**. Ignore non-relevant stack sections unless explicitly asked.
15
16## When to Apply
17
18Reference these guidelines when:
19- Designing new UI components or pages
20- Choosing color palettes and typography
21- Reviewing code for UX issues
22- Building landing pages or dashboards
23- Implementing accessibility requirements
24
25## Rule Categories by Priority
26
27| Priority | Category | Impact | Domain |
28|----------|----------|--------|--------|
29| 1 | Accessibility | CRITICAL | `ux` |
30| 2 | Touch & Interaction | CRITICAL | `ux` |
31| 3 | Performance | HIGH | `ux` |
32| 4 | Layout & Responsive | HIGH | `ux` |
33| 5 | Typography & Color | MEDIUM | `typography`, `color` |
34| 6 | Animation | MEDIUM | `ux` |
35| 7 | Style Selection | MEDIUM | `style`, `product` |
36| 8 | Charts & Data | LOW | `chart` |
37
38## Quick Reference
39
40### 1. Accessibility (CRITICAL)
41
42- `color-contrast` - Minimum 4.5:1 ratio for normal text
43- `focus-states` - Visible focus rings on interactive elements
44- `alt-text` - Descriptive alt text for meaningful images
45- `aria-labels` - aria-label for icon-only buttons
46- `keyboard-nav` - Tab order matches visual order
47- `form-labels` - Use label with for attribute
48
49### 2. Touch & Interaction (CRITICAL)
50
51- `touch-target-size` - Minimum 44x44px touch targets
52- `hover-vs-tap` - Use click/tap for primary interactions
53- `loading-buttons` - Disable button during async operations
54- `error-feedback` - Clear error messages near problem
55- `cursor-pointer` - Add cursor-pointer to clickable elements
56
57---
58
59## 🎯 TREIDO PROJECT: Tailwind v4 Token Syntax
60
61**This project uses Tailwind v4 with CSS variables.** Do NOT use arbitrary values or v3 syntax.
62
63### Touch Target Tokens
64
65```css
66/* globals.css defines these tokens */
67--spacing-touch-xs: 2rem; /* 32px - minimum WCAG */
68--spacing-touch-sm: 2.25rem; /* 36px - compact */
69--spacing-touch: 2.5rem; /* 40px - default */
70--spacing-touch-md: 2.75rem; /* 44px - Apple minimum */
71--spacing-touch-lg: 3rem; /* 48px - bottom nav */
72```
73
74### Correct Syntax
75
76```tsx
77// ❌ WRONG - Arbitrary values (v3 style)
78className="min-h-[44px] min-w-[44px]"
79className="h-11" // Magic number
80
81// ✅ CORRECT - Tailwind v4 CSS variable syntax
82className="min-h-(--spacing-touch-md) min-w-(--spacing-touch-md)"
83className="h-(--spacing-touch-md)"
84
85// ✅ CORRECT - Using size for square touch targets
86className="size-(--spacing-touch-md)"
87```
88
89### Common Treido Patterns
90
91| Use Case | Token | Tailwind v4 Class |
92|----------|-------|-------------------|
93| Bottom nav items | 48px | `h-(--spacing-touch-lg)` |
94| Header icons | 44px | `size-(--spacing-touch-md)` |
95| Button height | 44px | `h-(--spacing-button)` |
96| Compact button | 36px | `h-(--spacing-button-sm)` |
97| Input height | 44px | `h-(--spacing-input)` |
98| Category pills | 40px | `h-(--spacing-touch)` |
99
100### Full Example
101
102```tsx
103// Touch-friendly button with Treido tokens
104<button
105 className="
106 min-h-(--spacing-touch-md)
107 px-4
108 rounded-lg
109 bg-primary
110 text-primary-foreground
111 active:opacity-80
112 transition-opacity
113 "
114>
115 Tap me
116</button>
117```
118
119---
120
121### 3. Performance (HIGH)
122
123- `image-optimization` - Use WebP, srcset, lazy loading
124- `reduced-motion` - Check prefers-reduced-motion
125- `content-jumping` - Reserve space for async content
126
127### 4. Layout & Responsive (HIGH)
128
129- `viewport-meta` - width=device-width initial-scale=1
130- `readable-font-size` - Minimum 16px body text on mobile
131- `horizontal-scroll` - Ensure content fits viewport width
132- `z-index-management` - Define z-index scale (10, 20, 30, 50)
133
134### 5. Typography & Color (MEDIUM)
135
136- `line-height` - Use 1.5-1.75 for body text
137- `line-length` - Limit to 65-75 characters per line
138- `font-pairing` - Match heading/body font personalities
139
140### 6. Animation (MEDIUM)
141
142- `duration-timing` - Use 150-300ms for micro-interactions
143- `transform-performance` - Use transform/opacity, not width/height
144- `loading-states` - Skeleton screens or spinners
145
146### 7. Style Selection (MEDIUM)
147
148- `style-match` - Match style to product type
149- `consistency` - Use same style across all pages
150- `no-emoji-icons` - Use SVG icons, not emojis
151
152### 8. Charts & Data (LOW)
153
154- `chart-type` - Match chart type to data type
155- `color-guidance` - Use accessible color palettes
156- `data-table` - Provide table alternative for accessibility
157
158## How to Use
159
160Search specific domains using the CLI tool below.
161
162---
163
164## Prerequisites
165
166Check if Python is installed:
167
168```bash
169python3 --version || python --version
170```
171
172If Python is not installed, install it based on user's OS:
173
174**macOS:**
175```bash
176brew install python3
177```
178
179**Ubuntu/Debian:**
180```bash
181sudo apt update && sudo apt install python3
182```
183
184**Windows:**
185```powershell
186winget install Python.Python.3.12
187```
188
189---
190
191## How to Use This Skill
192
193When user requests UI/UX work (design, build, create, implement, review, fix, improve), follow this workflow:
194
195### Step 1: Analyze User Requirements
196
197Extract key information from user request:
198- **Product type**: SaaS, e-commerce, portfolio, dashboard, landing page, etc.
199- **Style keywords**: minimal, playful, professional, elegant, dark mode, etc.
200- **Industry**: healthcare, fintech, gaming, education, etc.
201- **Stack**: React, Vue, Next.js, or default to `html-tailwind`
202
203### Step 2: Generate Design System (REQUIRED)
204
205**Always start with `--design-system`** to get comprehensive recommendations with reasoning:
206
207```bash
208python3 .codex/skills/treido-ui-ux-pro-max/scripts/search.py "<product_type> <industry> <keywords>" --design-system [-p "Project Name"]
209```
210
211This command:
2121. Searches 5 domains in parallel (product, style, color, landing, typography)
2132. Applies reasoning rules from `ui-reasoning.csv` to select best matches
2143. Returns complete design system: pattern, style, colors, typography, effects
2154. Includes anti-patterns to avoid
216
217**Example:**
218```bash
219python3 .codex/skills/treido-ui-ux-pro-max/scripts/search.py "beauty spa wellness service" --design-system -p "Serenity Spa"
220```
221
222### Step 3: Supplement with Detailed Searches (as needed)
223
224After getting the design system, use domain searches to get additional details:
225
226```bash
227python3 .codex/skills/treido-ui-ux-pro-max/scripts/search.py "<keyword>" --domain <domain> [-n <max_results>]
228```
229
230**When to use detailed searches:**
231
232| Need | Domain | Example |
233|------|--------|---------|
234| More style options | `style` | `--domain style "glassmorphism dark"` |
235| Chart recommendations | `chart` | `--domain chart "real-time dashboard"` |
236| UX best practices | `ux` | `--domain ux "animation accessibility"` |
237| Alternative fonts | `typography` | `--domain typography "elegant luxury"` |
238| Landing structure | `landing` | `--domain landing "hero social-proof"` |
239
240### Step 4: Stack Guidelines (Default: html-tailwind)
241
242Get implementation-specific best practices. If user doesn't specify a stack, **default to `html-tailwind`**.
243
244```bash
245python3 .codex/skills/treido-ui-ux-pro-max/scripts/search.py "<keyword>" --stack html-tailwind
246```
247
248Available stacks: `html-tailwind`, `react`, `nextjs`, `vue`, `svelte`, `swiftui`, `react-native`, `flutter`, `shadcn`
249
250---
251
252## Search Reference
253
254### Available Domains
255
256| Domain | Use For | Example Keywords |
257|--------|---------|------------------|
258| `product` | Product type recommendations | SaaS, e-commerce, portfolio, healthcare, beauty, service |
259| `style` | UI styles, colors, effects | glassmorphism, minimalism, dark mode, brutalism |
260| `typography` | Font pairings, Google Fonts | elegant, playful, professional, modern |
261| `color` | Color palettes by product type | saas, ecommerce, healthcare, beauty, fintech, service |
262| `landing` | Page structure, CTA strategies | hero, hero-centric, testimonial, pricing, social-proof |
263| `chart` | Chart types, library recommendations | trend, comparison, timeline, funnel, pie |
264| `ux` | Best practices, anti-patterns | animation, accessibility, z-index, loading |
265| `react` | React/Next.js performance | waterfall, bundle, suspense, memo, rerender, cache |
266| `web` | Web interface guidelines | aria, focus, keyboard, semantic, virtualize |
267| `prompt` | AI prompts, CSS keywords | (style name) |
268
269### Available Stacks
270
271| Stack | Focus |
272|-------|-------|
273| `html-tailwind` | Tailwind utilities, responsive, a11y (DEFAULT) |
274| `react` | State, hooks, performance, patterns |
275| `nextjs` | SSR, routing, images, API routes |
276| `vue` | Composition API, Pinia, Vue Router |
277| `svelte` | Runes, stores, SvelteKit |
278| `swiftui` | Views, State, Navigation, Animation |
279| `react-native` | Components, Navigation, Lists |
280| `flutter` | Widgets, State, Layout, Theming |
281| `shadcn` | shadcn/ui components, theming, forms, patterns |
282
283---
284
285## Example Workflow
286
287**User request:** "Làm landing page cho dịch vụ chăm sóc da chuyên nghiệp"
288
289### Step 1: Analyze Requirements
290- Product type: Beauty/Spa service
291- Style keywords: elegant, professional, soft
292- Industry: Beauty/Wellness
293- Stack: html-tailwind (default)
294
295### Step 2: Generate Design System (REQUIRED)
296
297```bash
298python3 .codex/skills/treido-ui-ux-pro-max/scripts/search.py "beauty spa wellness service elegant" --design-system -p "Serenity Spa"
299```
300
301**Output:** Complete design system with pattern, style, colors, typography, effects, and anti-patterns.
302
303### Step 3: Supplement with Detailed Searches (as needed)
304
305```bash
306# Get UX guidelines for animation and accessibility
307python3 .codex/skills/treido-ui-ux-pro-max/scripts/search.py "animation accessibility" --domain ux
308
309# Get alternative typography options if needed
310python3 .codex/skills/treido-ui-ux-pro-max/scripts/search.py "elegant luxury serif" --domain typography
311```
312
313### Step 4: Stack Guidelines
314
315```bash
316python3 .codex/skills/treido-ui-ux-pro-max/scripts/search.py "layout responsive form" --stack html-tailwind
317```
318
319**Then:** Synthesize design system + detailed searches and implement the design.
320
321---
322
323## Output Formats
324
325The `--design-system` flag supports two output formats:
326
327```bash
328# ASCII box (default) - best for terminal display
329python3 .codex/skills/treido-ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system
330
331# Markdown - best for documentation
332python3 .codex/skills/treido-ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system -f markdown
333```
334
335---
336
337## Tips for Better Results
338
3391. **Be specific with keywords** - "healthcare SaaS dashboard" > "app"
3402. **Search multiple times** - Different keywords reveal different insights
3413. **Combine domains** - Style + Typography + Color = Complete design system
3424. **Always check UX** - Search "animation", "z-index", "accessibility" for common issues
3435. **Use stack flag** - Get implementation-specific best practices
3446. **Iterate** - If first search doesn't match, try different keywords
345
346---
347
348## Common Rules for Professional UI
349
350These are frequently overlooked issues that make UI look unprofessional:
351
352### Icons & Visual Elements
353
354| Rule | Do | Don't |
355|------|----|----- |
356| **No emoji icons** | Use SVG icons (Heroicons, Lucide, Simple Icons) | Use emojis like 🎨 🚀 ⚙️ as UI icons |
357| **Stable hover states** | Use color/opacity transitions on hover | Use scale transforms that shift layout |
358| **Correct brand logos** | Research official SVG from Simple Icons | Guess or use incorrect logo paths |
359| **Consistent icon sizing** | Use fixed viewBox (24x24) with w-6 h-6 | Mix different icon sizes randomly |
360
361### Interaction & Cursor
362
363| Rule | Do | Don't |
364|------|----|----- |
365| **Cursor pointer** | Add `cursor-pointer` to all clickable/hoverable cards | Leave default cursor on interactive elements |
366| **Hover feedback** | Provide visual feedback (color, shadow, border) | No indication element is interactive |
367| **Smooth transitions** | Use `transition-colors duration-200` | Instant state changes or too slow (>500ms) |
368
369### Light/Dark Mode Contrast
370
371| Rule | Do | Don't |
372|------|----|----- |
373| **Glass card light mode** | Use `bg-card` or `bg-surface` tokens | Use `bg-white/80` (opacity modifier) |
374| **Text contrast light** | Use `text-foreground` token | Use hardcoded hex like `#0F172A` |
375| **Muted text light** | Use `text-muted-foreground` token | Use palette colors like `gray-400` |
376| **Border visibility** | Use `border-border` token | Use palette like `border-gray-200` |
377
378### Layout & Spacing
379
380| Rule | Do | Don't |
381|------|----|----- |
382| **Floating navbar** | Add `top-4 left-4 right-4` spacing | Stick navbar to `top-0 left-0 right-0` |
383| **Content padding** | Account for fixed navbar height | Let content hide behind fixed elements |
384| **Consistent max-width** | Use same `max-w-6xl` or `max-w-7xl` | Mix different container widths |
385
386---
387
388## Pre-Delivery Checklist
389
390Before delivering UI code, verify these items:
391
392### Visual Quality
393- [ ] No emojis used as icons (use SVG instead)
394- [ ] All icons from consistent icon set (Heroicons/Lucide)
395- [ ] Brand logos are correct (verified from Simple Icons)
396- [ ] Hover states don't cause layout shift
397- [ ] Use theme colors directly (bg-primary) not var() wrapper
398
399### Interaction
400- [ ] All clickable elements have `cursor-pointer`
401- [ ] Hover states provide clear visual feedback
402- [ ] Transitions are smooth (150-300ms)
403- [ ] Focus states visible for keyboard navigation
404
405### Light/Dark Mode
406- [ ] Light mode text has sufficient contrast (4.5:1 minimum)
407- [ ] Glass/transparent elements visible in light mode
408- [ ] Borders visible in both modes
409- [ ] Test both modes before delivery
410
411### Layout
412- [ ] Floating elements have proper spacing from edges
413- [ ] No content hidden behind fixed navbars
414- [ ] Responsive at 375px, 768px, 1024px, 1440px
415- [ ] No horizontal scroll on mobile
416
417### Accessibility
418- [ ] All images have alt text
419- [ ] Form inputs have labels
420- [ ] Color is not the only indicator
421- [ ] `prefers-reduced-motion` respected
majiayu000