ui-ux-pro-max
UI/UX design-system intelligence - 84 styles, 192 palettes, 74 font pairings, 25 charts, 99 UX guidelines across 22 stacks (searchable dataset + CLI). Internal genjutsu module: loaded by /genjutsu:cast and /genjutsu:paint, not invoked directly.
Install
npx skills add https://github.com/AThevon/genjutsu/tree/main/skills/_jutsu/ui-ux-pro-max
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install athevon-genjutsu@llmmart
git clone https://github.com/AThevon/genjutsu.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole athevon/genjutsu collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Version-sensitive. Every API name, SDK gate and browser-support claim below was verified on 2026-09-08 against primary sources. What against, and when, is in
_jutsu/VERSIONS.md. If that date is old, re-verify before acting on a version number.
UI/UX Pro Max - Design Intelligence
Comprehensive design guide for web and mobile applications. Contains 84 styles, 192 color palettes, 74 font pairings, 99 UX guidelines, and 25 chart types across 22 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
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
Requires python3 (available by default in the Claude Code shell and in claude.ai's code-execution sandbox). This skill does not install anything.
Always pass -f markdown on --design-system. The default is ascii, which is built for a
terminal: it emits about 7,000 bytes carrying raw ANSI colour escapes, and hex_to_ansi has no
isatty guard, so those escapes survive being piped and land in the context window as garbage.
-f markdown returns the same information in about 2,100 bytes of clean markdown. The consumer
here is a model, not a terminal, so this is a 3.3x token reduction on the most-run command in
this skill.
How to Use This Skill
When user requests UI/UX work (design, build, create, implement, review, fix, improve), follow this workflow:
Every command below runs in the same shell call as this block. Shell state does not survive
between calls, and the working directory is not guaranteed to either, so UIUX_DIR is derived
again each time and every command names the script by its full path. The block tries, in order:
$SKILL_BASE/ui-ux-pro-max when an orchestrator's skill-base block ran earlier in the same call;
a directory you name yourself by putting UIUX_DIR='/absolute/path/to/ui-ux-pro-max' in front of
the block; this skill's own directory when the host substitutes CLAUDE_SKILL_DIR (a standalone
install); then a bounded search of the usual skills
directories. When you already know the absolute path, you may write it in place of $UIUX_DIR.
# Commands run from the project, so --persist writes to the project root and
# never into the skill directory.
PROJECT_ROOT="$PWD"
uiux_given="${UIUX_DIR:-}"
UIUX_DIR=""
for uiux_c in "${SKILL_BASE:+$SKILL_BASE/ui-ux-pro-max}" "$uiux_given" "${CLAUDE_SKILL_DIR}"; do
[ -n "$uiux_c" ] && [ -f "$uiux_c/scripts/search.py" ] && { UIUX_DIR="$uiux_c"; break; }
done
if [ -z "$UIUX_DIR" ]; then
for uiux_root in "$HOME/.agents/skills" "$HOME/.claude/skills" "$HOME/.claude/plugins" /mnt/skills; do
[ -d "$uiux_root" ] || continue
uiux_hit="$(find -L "$uiux_root" -maxdepth 9 -type f -path '*/ui-ux-pro-max/scripts/search.py' 2>/dev/null | sort -V | tail -1)"
[ -n "$uiux_hit" ] && { UIUX_DIR="${uiux_hit%/scripts/search.py}"; break; }
done
fi
[ -n "$UIUX_DIR" ] || echo "genjutsu: ui-ux-pro-max not found. Say so in one line and derive the design system from the thesis by hand." >&2
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 "$UIUX_DIR/scripts/search.py" "<product_type> <industry> <keywords>" --design-system [-p "Project Name"] -f markdown
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 "$UIUX_DIR/scripts/search.py" "beauty spa wellness service" --design-system -p "Serenity Spa" -f markdown
Step 2b: Persist Design System (Master + Overrides Pattern)
To save the design system for hierarchical retrieval across sessions, add --persist (point --output-dir at the project root so files land there, not in the skill dir):
python3 "$UIUX_DIR/scripts/search.py" "<query>" --design-system --persist -p "Project Name" --output-dir "$PROJECT_ROOT" -f markdown
This creates:
design-system/<project-slug>/MASTER.md- Global Source of Truth with all design rulesdesign-system/<project-slug>/pages/- Folder for page-specific overrides
--persist skips writing if MASTER.md already exists; add --force to overwrite.
With page-specific override:
python3 "$UIUX_DIR/scripts/search.py" "<query>" --design-system --persist -p "Project Name" --page "dashboard" --output-dir "$PROJECT_ROOT" -f markdown
This also creates:
design-system/<project-slug>/pages/dashboard.md- Page-specific deviations from Master
How hierarchical retrieval works:
- When building a specific page (e.g., "Checkout"), first check
design-system/<project-slug>/pages/checkout.md - If the page file exists, its rules override the Master file
- If not, use
design-system/<project-slug>/MASTER.mdexclusively
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 3: Supplement with Detailed Searches (as needed)
After getting the design system, use domain searches to get additional details:
python3 "$UIUX_DIR/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 "$UIUX_DIR/scripts/search.py" "<keyword>" --stack html-tailwind
Available stacks: html-tailwind, react, nextjs, astro, vue, nuxtjs, nuxt-ui, svelte, swiftui, react-native, flutter, shadcn, jetpack-compose, threejs, angular, laravel, javafx, wpf, winui, avalonia, uno, uwp
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 (full token sets) | 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 |
icons |
Icon set + import guidance | outline, solid, brand, navigation |
react |
React/Next.js performance | waterfall, bundle, suspense, memo, rerender, cache |
web |
App/web interface guidelines | aria, focus, keyboard, semantic, virtualize |
gsap |
Motion snippets (feeds the --motion dial) |
reveal, parallax, stagger, scroll |
google-fonts |
Google Fonts lookup | serif, mono, display, variable |
Available Stacks
| Stack | Focus |
|---|---|
html-tailwind |
Tailwind utilities, responsive, a11y (DEFAULT) |
react |
State, hooks, performance, patterns |
nextjs |
SSR, routing, images, API routes |
astro |
Islands architecture, partial hydration, content-driven |
vue |
Composition API, Pinia, Vue Router |
nuxtjs |
Nuxt 3, composables, SSR/SSG, auto-imports |
nuxt-ui |
Nuxt UI components, theming, forms |
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 |
threejs |
Three.js scenes, materials, R3F patterns |
angular |
Components, signals, RxJS, standalone APIs |
laravel |
Blade, Livewire, Tailwind, form patterns |
javafx |
Scene graph, FXML, CSS, controls |
wpf |
XAML, MVVM, bindings, styles |
winui |
WinUI 3, XAML, Fluent, bindings |
avalonia |
Cross-platform XAML, MVVM, styling |
uno |
Uno Platform, WinUI XAML cross-target |
uwp |
UWP XAML, Fluent, adaptive UI |
Example Workflow
User request: "Build a landing page for a professional skincare service"
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 "$UIUX_DIR/scripts/search.py" "beauty spa wellness service elegant" --design-system -p "Serenity Spa" -f markdown
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 "$UIUX_DIR/scripts/search.py" "animation accessibility" --domain ux
# Get alternative typography options if needed
python3 "$UIUX_DIR/scripts/search.py" "elegant luxury serif" --domain typography
Step 4: Stack Guidelines
python3 "$UIUX_DIR/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 "$UIUX_DIR/scripts/search.py" "fintech crypto" --design-system -f markdown
# Markdown - best for documentation
python3 "$UIUX_DIR/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 |
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
Files (genjutsu)
-
data
-
stacks
-
angular.csv 17.7 KB · in bundle
-
astro.csv 11.6 KB · in bundle
-
avalonia.csv 25 KB · in bundle
-
flutter.csv 10.2 KB · in bundle
-
html-tailwind.csv 11 KB · in bundle
-
javafx.csv 30.1 KB · in bundle
-
jetpack-compose.csv 8 KB · in bundle
-
laravel.csv 18.1 KB · in bundle
-
nextjs.csv 12.2 KB · in bundle
-
nuxt-ui.csv 20.7 KB · in bundle
-
nuxtjs.csv 16.2 KB · in bundle
-
react-native.csv 9.7 KB · in bundle
-
react.csv 12.7 KB · in bundle
-
shadcn.csv 15.5 KB · in bundle
-
svelte.csv 10.8 KB · in bundle
-
swiftui.csv 10.6 KB · in bundle
-
threejs.csv 43.8 KB · in bundle
-
uno.csv 26.8 KB · in bundle
-
uwp.csv 22.3 KB · in bundle
-
vue.csv 10.7 KB · in bundle
-
winui.csv 24.6 KB · in bundle
-
wpf.csv 22 KB · in bundle
-
-
app-interface.csv 9.5 KB · in bundle
-
charts.csv 18.9 KB · in bundle
-
colors.csv 37.8 KB · in bundle
-
google-fonts.csv 725.9 KB · in bundle
-
icons.csv 20.2 KB · in bundle
-
landing.csv 16.3 KB · in bundle
-
motion.csv 10.3 KB · in bundle
-
products.csv 71.8 KB · in bundle
-
react-performance.csv 14.5 KB · in bundle
-
styles.csv 139.3 KB · in bundle
-
typography.csv 48.7 KB · in bundle
-
ui-reasoning.csv 51.7 KB · in bundle
-
ux-guidelines.csv 18.2 KB · in bundle
-
-
references
-
pro-rules.md 9.4 KB
Loading… -
quick-reference.md 21.1 KB
Loading…
-
-
scripts
-
tests
-
test_core.py 5.8 KB
Loading…
-
-
core.py 18.4 KB
Loading… -
design_system.py 58 KB
Loading… -
search.py 8.5 KB
Loading… -
validate_data.py 4.1 KB
Loading…
-
-
LICENSE-upstream.txt 1 KB
Loading… -
SKILL.md 16.9 KB
--- name: ui-ux-pro-max description: "UI/UX design-system intelligence - 84 styles, 192 palettes, 74 font pairings, 25 charts, 99 UX guidelines across 22 stacks (searchable dataset + CLI). Internal genjutsu module: loaded by /genjutsu:cast and /genjutsu:paint, not invoked directly." metadata: internal: true --- > **Version-sensitive.** Every API name, SDK gate and browser-support claim below was > verified on **2026-09-08** against primary sources. What against, and when, is in > `_jutsu/VERSIONS.md`. If that date is old, re-verify before acting on a version number. # UI/UX Pro Max - Design Intelligence Comprehensive design guide for web and mobile applications. Contains 84 styles, 192 color palettes, 74 font pairings, 99 UX guidelines, and 25 chart types across 22 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 ## 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 text - `focus-states` - Visible focus rings on interactive elements - `alt-text` - Descriptive alt text for meaningful images - `aria-labels` - aria-label for icon-only buttons - `keyboard-nav` - Tab order matches visual order - `form-labels` - Use label with for attribute ### 2. Touch & Interaction (CRITICAL) - `touch-target-size` - Minimum 44x44px touch targets - `hover-vs-tap` - Use click/tap for primary interactions - `loading-buttons` - Disable button during async operations - `error-feedback` - Clear error messages near problem - `cursor-pointer` - Add cursor-pointer to clickable elements ### 3. Performance (HIGH) - `image-optimization` - Use WebP, srcset, lazy loading - `reduced-motion` - Check prefers-reduced-motion - `content-jumping` - Reserve space for async content ### 4. Layout & Responsive (HIGH) - `viewport-meta` - width=device-width initial-scale=1 - `readable-font-size` - Minimum 16px body text on mobile - `horizontal-scroll` - Ensure content fits viewport width - `z-index-management` - Define z-index scale (10, 20, 30, 50) ### 5. Typography & Color (MEDIUM) - `line-height` - Use 1.5-1.75 for body text - `line-length` - Limit to 65-75 characters per line - `font-pairing` - Match heading/body font personalities ### 6. Animation (MEDIUM) - `duration-timing` - Use 150-300ms for micro-interactions - `transform-performance` - Use transform/opacity, not width/height - `loading-states` - Skeleton screens or spinners ### 7. Style Selection (MEDIUM) - `style-match` - Match style to product type - `consistency` - Use same style across all pages - `no-emoji-icons` - Use SVG icons, not emojis ### 8. Charts & Data (LOW) - `chart-type` - Match chart type to data type - `color-guidance` - Use accessible color palettes - `data-table` - Provide table alternative for accessibility ## How to Use Search specific domains using the CLI tool below. --- ## Prerequisites Requires `python3` (available by default in the Claude Code shell and in claude.ai's code-execution sandbox). This skill does not install anything. **Always pass `-f markdown` on `--design-system`.** The default is `ascii`, which is built for a terminal: it emits about 7,000 bytes carrying raw ANSI colour escapes, and `hex_to_ansi` has no isatty guard, so those escapes survive being piped and land in the context window as garbage. `-f markdown` returns the same information in about 2,100 bytes of clean markdown. The consumer here is a model, not a terminal, so this is a 3.3x token reduction on the most-run command in this skill. --- ## How to Use This Skill When user requests UI/UX work (design, build, create, implement, review, fix, improve), follow this workflow: **Every command below runs in the same shell call as this block.** Shell state does not survive between calls, and the working directory is not guaranteed to either, so `UIUX_DIR` is derived again each time and every command names the script by its full path. The block tries, in order: `$SKILL_BASE/ui-ux-pro-max` when an orchestrator's skill-base block ran earlier in the same call; a directory you name yourself by putting `UIUX_DIR='/absolute/path/to/ui-ux-pro-max'` in front of the block; this skill's own directory when the host substitutes `CLAUDE_SKILL_DIR` (a standalone install); then a bounded search of the usual skills directories. When you already know the absolute path, you may write it in place of `$UIUX_DIR`. <!-- genjutsu:uiux-dir:start --> ```bash # Commands run from the project, so --persist writes to the project root and # never into the skill directory. PROJECT_ROOT="$PWD" uiux_given="${UIUX_DIR:-}" UIUX_DIR="" for uiux_c in "${SKILL_BASE:+$SKILL_BASE/ui-ux-pro-max}" "$uiux_given" "${CLAUDE_SKILL_DIR}"; do [ -n "$uiux_c" ] && [ -f "$uiux_c/scripts/search.py" ] && { UIUX_DIR="$uiux_c"; break; } done if [ -z "$UIUX_DIR" ]; then for uiux_root in "$HOME/.agents/skills" "$HOME/.claude/skills" "$HOME/.claude/plugins" /mnt/skills; do [ -d "$uiux_root" ] || continue uiux_hit="$(find -L "$uiux_root" -maxdepth 9 -type f -path '*/ui-ux-pro-max/scripts/search.py' 2>/dev/null | sort -V | tail -1)" [ -n "$uiux_hit" ] && { UIUX_DIR="${uiux_hit%/scripts/search.py}"; break; } done fi [ -n "$UIUX_DIR" ] || echo "genjutsu: ui-ux-pro-max not found. Say so in one line and derive the design system from the thesis by hand." >&2 ``` <!-- genjutsu:uiux-dir:end --> ### 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: ```bash python3 "$UIUX_DIR/scripts/search.py" "<product_type> <industry> <keywords>" --design-system [-p "Project Name"] -f markdown ``` This command: 1. Searches 5 domains in parallel (product, style, color, landing, typography) 2. Applies reasoning rules from `ui-reasoning.csv` to select best matches 3. Returns complete design system: pattern, style, colors, typography, effects 4. Includes anti-patterns to avoid **Example:** ```bash python3 "$UIUX_DIR/scripts/search.py" "beauty spa wellness service" --design-system -p "Serenity Spa" -f markdown ``` ### Step 2b: Persist Design System (Master + Overrides Pattern) To save the design system for **hierarchical retrieval across sessions**, add `--persist` (point `--output-dir` at the project root so files land there, not in the skill dir): ```bash python3 "$UIUX_DIR/scripts/search.py" "<query>" --design-system --persist -p "Project Name" --output-dir "$PROJECT_ROOT" -f markdown ``` This creates: - `design-system/<project-slug>/MASTER.md` - Global Source of Truth with all design rules - `design-system/<project-slug>/pages/` - Folder for page-specific overrides `--persist` skips writing if `MASTER.md` already exists; add `--force` to overwrite. **With page-specific override:** ```bash python3 "$UIUX_DIR/scripts/search.py" "<query>" --design-system --persist -p "Project Name" --page "dashboard" --output-dir "$PROJECT_ROOT" -f markdown ``` This also creates: - `design-system/<project-slug>/pages/dashboard.md` - Page-specific deviations from Master **How hierarchical retrieval works:** 1. When building a specific page (e.g., "Checkout"), first check `design-system/<project-slug>/pages/checkout.md` 2. If the page file exists, its rules **override** the Master file 3. If not, use `design-system/<project-slug>/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 3: Supplement with Detailed Searches (as needed) After getting the design system, use domain searches to get additional details: ```bash python3 "$UIUX_DIR/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`**. ```bash python3 "$UIUX_DIR/scripts/search.py" "<keyword>" --stack html-tailwind ``` Available stacks: `html-tailwind`, `react`, `nextjs`, `astro`, `vue`, `nuxtjs`, `nuxt-ui`, `svelte`, `swiftui`, `react-native`, `flutter`, `shadcn`, `jetpack-compose`, `threejs`, `angular`, `laravel`, `javafx`, `wpf`, `winui`, `avalonia`, `uno`, `uwp` --- ## 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 (full token sets) | 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 | | `icons` | Icon set + import guidance | outline, solid, brand, navigation | | `react` | React/Next.js performance | waterfall, bundle, suspense, memo, rerender, cache | | `web` | App/web interface guidelines | aria, focus, keyboard, semantic, virtualize | | `gsap` | Motion snippets (feeds the `--motion` dial) | reveal, parallax, stagger, scroll | | `google-fonts` | Google Fonts lookup | serif, mono, display, variable | ### Available Stacks | Stack | Focus | |-------|-------| | `html-tailwind` | Tailwind utilities, responsive, a11y (DEFAULT) | | `react` | State, hooks, performance, patterns | | `nextjs` | SSR, routing, images, API routes | | `astro` | Islands architecture, partial hydration, content-driven | | `vue` | Composition API, Pinia, Vue Router | | `nuxtjs` | Nuxt 3, composables, SSR/SSG, auto-imports | | `nuxt-ui` | Nuxt UI components, theming, forms | | `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 | | `threejs` | Three.js scenes, materials, R3F patterns | | `angular` | Components, signals, RxJS, standalone APIs | | `laravel` | Blade, Livewire, Tailwind, form patterns | | `javafx` | Scene graph, FXML, CSS, controls | | `wpf` | XAML, MVVM, bindings, styles | | `winui` | WinUI 3, XAML, Fluent, bindings | | `avalonia` | Cross-platform XAML, MVVM, styling | | `uno` | Uno Platform, WinUI XAML cross-target | | `uwp` | UWP XAML, Fluent, adaptive UI | --- ## Example Workflow **User request:** "Build a landing page for a professional skincare service" ### 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) ```bash python3 "$UIUX_DIR/scripts/search.py" "beauty spa wellness service elegant" --design-system -p "Serenity Spa" -f markdown ``` **Output:** Complete design system with pattern, style, colors, typography, effects, and anti-patterns. ### Step 3: Supplement with Detailed Searches (as needed) ```bash # Get UX guidelines for animation and accessibility python3 "$UIUX_DIR/scripts/search.py" "animation accessibility" --domain ux # Get alternative typography options if needed python3 "$UIUX_DIR/scripts/search.py" "elegant luxury serif" --domain typography ``` ### Step 4: Stack Guidelines ```bash python3 "$UIUX_DIR/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: ```bash # ASCII box (default) - best for terminal display python3 "$UIUX_DIR/scripts/search.py" "fintech crypto" --design-system -f markdown # Markdown - best for documentation python3 "$UIUX_DIR/scripts/search.py" "fintech crypto" --design-system -f markdown ``` --- ## Tips for Better Results 1. **Be specific with keywords** - "healthcare SaaS dashboard" > "app" 2. **Search multiple times** - Different keywords reveal different insights 3. **Combine domains** - Style + Typography + Color = Complete design system 4. **Always check UX** - Search "animation", "z-index", "accessibility" for common issues 5. **Use stack flag** - Get implementation-specific best practices 6. **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-motion` respected -
UPSTREAM.md 4.9 KB
Loading…
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.