UI/UX Pro Max - Design Intelligence
Overview
This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/ui-ux-pro-max from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
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.
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: How to Use, Prerequisites, How to Use This Skill, Output Formats, Tips for Better Results, Pre-Delivery Checklist.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
- Designing new UI components or pages
- Choosing color palettes and typography
- Reviewing code for UX issues
- Building landing pages or dashboards
- Implementing accessibility requirements
- Use when the request clearly matches the imported source intent: Comprehensive design guide for web and mobile applications. Use when designing new UI components or pages, choosing color palettes and typography, or reviewing code for UX issues.
Operating Table
| Situation |
Start here |
Why it matters |
| First-time use |
metadata.json |
Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow |
| Provenance review |
ORIGIN.md |
Gives reviewers a plain-language audit trail for the imported source |
| Workflow execution |
scripts/core.py |
Starts with the smallest copied file that materially changes execution |
| Supporting context |
scripts/design_system.py |
Adds the next most relevant copied source file without loading the entire package |
| Handoff decision |
## Related Skills |
Helps the operator switch to a stronger native skill when the task drifts |
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
- Product type: Beauty/Spa service
- Style keywords: elegant, professional, soft
- Industry: Beauty/Wellness
- Stack: html-tailwind (default)
- Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
- Read the overview and provenance files before loading any copied upstream support files.
- Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
Imported Workflow Notes
Imported: 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 .claude/skills/ui-ux-pro-max/scripts/search.py "beauty spa wellness service elegant" --design-system -p "Serenity Spa"
Output: Complete design system with pattern, style, colors, typography, effects, and anti-patterns.
Step 3: Supplement with Detailed Searches (as needed)
# Get UX guidelines for animation and accessibility
python3 .claude/skills/ui-ux-pro-max/scripts/search.py "animation accessibility" --domain ux
# Get alternative typography options if needed
python3 .claude/skills/ui-ux-pro-max/scripts/search.py "elegant luxury serif" --domain typography
Step 4: Stack Guidelines
python3 .claude/skills/ui-ux-pro-max/scripts/search.py "layout responsive form" --stack html-tailwind
Then: Synthesize design system + detailed searches and implement the design.
Imported: How to Use
Search specific domains using the CLI tool below.
Examples
Example 1: Ask for the upstream workflow directly
Use @ui-ux-pro-max to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @ui-ux-pro-max against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @ui-ux-pro-max for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @ui-ux-pro-max using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
- 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
Imported Operating Notes
Imported: 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 |
Imported: 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 |
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/ui-ux-pro-max, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@20-andruia-niche-intelligence-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@advogado-criminal-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@advogado-especialista-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@agent-memory-systems-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
| Resource family |
What it gives the reviewer |
Example path |
references |
copied reference notes, guides, or background material from upstream |
references/n/a |
examples |
worked examples or reusable prompts copied from upstream |
examples/n/a |
scripts |
upstream helper scripts that change execution or validation |
scripts/core.py |
agents |
routing or delegation notes that are genuinely part of the imported package |
agents/n/a |
assets |
supporting assets or schemas copied from the source package |
assets/n/a |
- core.py
- design_system.py
- search.py
- charts.csv
- colors.csv
- icons.csv
Imported Reference Notes
Imported: 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
Imported: 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 |
Imported: 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
Imported: 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 .claude/skills/ui-ux-pro-max/scripts/search.py "<product_type> <industry> <keywords>" --design-system [-p "Project Name"]
This command:
- Searches 5 domains in parallel (product, style, color, landing, typography)
- Applies reasoning rules from
ui-reasoning.csv to select best matches
- Returns complete design system: pattern, style, colors, typography, effects
- Includes anti-patterns to avoid
Example:
python3 .claude/skills/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 .claude/skills/ui-ux-pro-max/scripts/search.py "<keyword>" --domain <domain> [-n <max_results>]
When to use detailed searches:
| Need |
Domain |
Example |
| More style options |
style |
--domain style "glassmorphism dark" |
| Chart recommendations |
chart |
--domain chart "real-time dashboard" |
| UX best practices |
ux |
--domain ux "animation accessibility" |
| Alternative fonts |
typography |
--domain typography "elegant luxury" |
| Landing structure |
landing |
--domain landing "hero social-proof" |
Step 4: Stack Guidelines (Default: html-tailwind)
Get implementation-specific best practices. If user doesn't specify a stack, default to html-tailwind.
python3 .claude/skills/ui-ux-pro-max/scripts/search.py "<keyword>" --stack html-tailwind
Available stacks: html-tailwind, react, nextjs, vue, svelte, swiftui, react-native, flutter, shadcn
Imported: Output Formats
The --design-system flag supports two output formats:
# ASCII box (default) - best for terminal display
python3 .claude/skills/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system
# Markdown - best for documentation
python3 .claude/skills/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system -f markdown
Imported: 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
Imported: Pre-Delivery Checklist
Before delivering UI code, verify these items:
Visual Quality
Interaction
Light/Dark Mode
Layout
Accessibility
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Imported: Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
1---2name: ui-ux-pro-max3description: "UI/UX Pro Max - Design Intelligence workflow skill. Use this skill when the user needs Comprehensive design guide for web and mobile applications. Use when designing new UI components or pages, choosing color palettes and typography, or reviewing code for UX issues and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off."4version: "0.0.1"5category: design6tags: ["ui-ux-pro-max", "comprehensive", "design", "guide", "for", "web", "and", "mobile"]7complexity: advanced8risk: safe9tools: ["codex-cli", "claude-code", "cursor", "gemini-cli", "opencode"]10source: community11author: "sickn33"12date_added: "2026-04-15"13date_updated: "2026-05-17"14metadata:15 source: https://skillmd.com/skills/belentani7/ui-ux-pro-max16---1718# UI/UX Pro Max - Design Intelligence1920## Overview2122This public intake copy packages `plugins/antigravity-awesome-skills-claude/skills/ui-ux-pro-max` from `https://github.com/sickn33/antigravity-awesome-skills` into the native Omni Skills editorial shape without hiding its origin.2324Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.2526This intake keeps the copied upstream files intact and uses the `external_source` block in `metadata.json` plus `ORIGIN.md` as the provenance anchor for review.2728# 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.2930Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: How to Use, Prerequisites, How to Use This Skill, Output Formats, Tips for Better Results, Pre-Delivery Checklist.3132## When to Use This Skill3334Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.3536- Designing new UI components or pages37- Choosing color palettes and typography38- Reviewing code for UX issues39- Building landing pages or dashboards40- Implementing accessibility requirements41- Use when the request clearly matches the imported source intent: Comprehensive design guide for web and mobile applications. Use when designing new UI components or pages, choosing color palettes and typography, or reviewing code for UX issues.4243## Operating Table4445| Situation | Start here | Why it matters |46| --- | --- | --- |47| First-time use | `metadata.json` | Confirms repository, branch, commit, and imported path through the `external_source` block before touching the copied workflow |48| Provenance review | `ORIGIN.md` | Gives reviewers a plain-language audit trail for the imported source |49| Workflow execution | `scripts/core.py` | Starts with the smallest copied file that materially changes execution |50| Supporting context | `scripts/design_system.py` | Adds the next most relevant copied source file without loading the entire package |51| Handoff decision | `## Related Skills` | Helps the operator switch to a stronger native skill when the task drifts |5253## Workflow5455This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.56571. Product type: Beauty/Spa service582. Style keywords: elegant, professional, soft593. Industry: Beauty/Wellness604. Stack: html-tailwind (default)615. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.626. Read the overview and provenance files before loading any copied upstream support files.637. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.6465### Imported Workflow Notes6667#### Imported: Example Workflow6869**User request:** "Làm landing page cho dịch vụ chăm sóc da chuyên nghiệp"7071### Step 1: Analyze Requirements72- Product type: Beauty/Spa service73- Style keywords: elegant, professional, soft74- Industry: Beauty/Wellness75- Stack: html-tailwind (default)7677### Step 2: Generate Design System (REQUIRED)7879```bash80python3 .claude/skills/ui-ux-pro-max/scripts/search.py "beauty spa wellness service elegant" --design-system -p "Serenity Spa"81```8283**Output:** Complete design system with pattern, style, colors, typography, effects, and anti-patterns.8485### Step 3: Supplement with Detailed Searches (as needed)8687```bash88# Get UX guidelines for animation and accessibility89python3 .claude/skills/ui-ux-pro-max/scripts/search.py "animation accessibility" --domain ux9091# Get alternative typography options if needed92python3 .claude/skills/ui-ux-pro-max/scripts/search.py "elegant luxury serif" --domain typography93```9495### Step 4: Stack Guidelines9697```bash98python3 .claude/skills/ui-ux-pro-max/scripts/search.py "layout responsive form" --stack html-tailwind99```100101**Then:** Synthesize design system + detailed searches and implement the design.102103---104105#### Imported: How to Use106107Search specific domains using the CLI tool below.108109---110111## Examples112113### Example 1: Ask for the upstream workflow directly114115```text116Use @ui-ux-pro-max to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.117```118119**Explanation:** This is the safest starting point when the operator needs the imported workflow, but not the entire repository.120121### Example 2: Ask for a provenance-grounded review122123```text124Review @ui-ux-pro-max against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.125```126127**Explanation:** Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.128129### Example 3: Narrow the copied support files before execution130131```text132Use @ui-ux-pro-max for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.133```134135**Explanation:** This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.136137### Example 4: Build a reviewer packet138139```text140Review @ui-ux-pro-max using the copied upstream files plus provenance, then summarize any gaps before merge.141```142143**Explanation:** This is useful when the PR is waiting for human review and you want a repeatable audit packet.144145146147## Best Practices148149Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.150151- Priority - Category - Impact - Domain152- 1 - Accessibility - CRITICAL - ux153- 2 - Touch & Interaction - CRITICAL - ux154- 3 - Performance - HIGH - ux155- 4 - Layout & Responsive - HIGH - ux156- 5 - Typography & Color - MEDIUM - typography, color157- 6 - Animation - MEDIUM - ux158159### Imported Operating Notes160161#### Imported: Rule Categories by Priority162163| Priority | Category | Impact | Domain |164|----------|----------|--------|--------|165| 1 | Accessibility | CRITICAL | `ux` |166| 2 | Touch & Interaction | CRITICAL | `ux` |167| 3 | Performance | HIGH | `ux` |168| 4 | Layout & Responsive | HIGH | `ux` |169| 5 | Typography & Color | MEDIUM | `typography`, `color` |170| 6 | Animation | MEDIUM | `ux` |171| 7 | Style Selection | MEDIUM | `style`, `product` |172| 8 | Charts & Data | LOW | `chart` |173174#### Imported: Common Rules for Professional UI175176These are frequently overlooked issues that make UI look unprofessional:177178### Icons & Visual Elements179180| Rule | Do | Don't |181|------|----|----- |182| **No emoji icons** | Use SVG icons (Heroicons, Lucide, Simple Icons) | Use emojis like 🎨 🚀 ⚙️ as UI icons |183| **Stable hover states** | Use color/opacity transitions on hover | Use scale transforms that shift layout |184| **Correct brand logos** | Research official SVG from Simple Icons | Guess or use incorrect logo paths |185| **Consistent icon sizing** | Use fixed viewBox (24x24) with w-6 h-6 | Mix different icon sizes randomly |186187### Interaction & Cursor188189| Rule | Do | Don't |190|------|----|----- |191| **Cursor pointer** | Add `cursor-pointer` to all clickable/hoverable cards | Leave default cursor on interactive elements |192| **Hover feedback** | Provide visual feedback (color, shadow, border) | No indication element is interactive |193| **Smooth transitions** | Use `transition-colors duration-200` | Instant state changes or too slow (>500ms) |194195### Light/Dark Mode Contrast196197| Rule | Do | Don't |198|------|----|----- |199| **Glass card light mode** | Use `bg-white/80` or higher opacity | Use `bg-white/10` (too transparent) |200| **Text contrast light** | Use `#0F172A` (slate-900) for text | Use `#94A3B8` (slate-400) for body text |201| **Muted text light** | Use `#475569` (slate-600) minimum | Use gray-400 or lighter |202| **Border visibility** | Use `border-gray-200` in light mode | Use `border-white/10` (invisible) |203204### Layout & Spacing205206| Rule | Do | Don't |207|------|----|----- |208| **Floating navbar** | Add `top-4 left-4 right-4` spacing | Stick navbar to `top-0 left-0 right-0` |209| **Content padding** | Account for fixed navbar height | Let content hide behind fixed elements |210| **Consistent max-width** | Use same `max-w-6xl` or `max-w-7xl` | Mix different container widths |211212---213214## Troubleshooting215216### Problem: The operator skipped the imported context and answered too generically217218**Symptoms:** The result ignores the upstream workflow in `plugins/antigravity-awesome-skills-claude/skills/ui-ux-pro-max`, fails to mention provenance, or does not use any copied source files at all.219**Solution:** Re-open `metadata.json`, `ORIGIN.md`, and the most relevant copied upstream files. Check the `external_source` block first, then restate the provenance before continuing.220221### Problem: The imported workflow feels incomplete during review222223**Symptoms:** Reviewers can see the generated `SKILL.md`, but they cannot quickly tell which references, examples, or scripts matter for the current task.224**Solution:** Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.225226### Problem: The task drifted into a different specialization227228**Symptoms:** The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.229**Solution:** Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.230231232233## Related Skills234235- `@20-andruia-niche-intelligence-v2` - Use when the work is better handled by that native specialization after this imported skill establishes context.236- `@advogado-criminal-v2` - Use when the work is better handled by that native specialization after this imported skill establishes context.237- `@advogado-especialista-v2` - Use when the work is better handled by that native specialization after this imported skill establishes context.238- `@agent-memory-systems-v2` - Use when the work is better handled by that native specialization after this imported skill establishes context.239240## Additional Resources241242Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.243244| Resource family | What it gives the reviewer | Example path |245| --- | --- | --- |246| `references` | copied reference notes, guides, or background material from upstream | `references/n/a` |247| `examples` | worked examples or reusable prompts copied from upstream | `examples/n/a` |248| `scripts` | upstream helper scripts that change execution or validation | `scripts/core.py` |249| `agents` | routing or delegation notes that are genuinely part of the imported package | `agents/n/a` |250| `assets` | supporting assets or schemas copied from the source package | `assets/n/a` |251252- [core.py](scripts/core.py)253- [design_system.py](scripts/design_system.py)254- [search.py](scripts/search.py)255- [charts.csv](data/charts.csv)256- [colors.csv](data/colors.csv)257- [icons.csv](data/icons.csv)258259### Imported Reference Notes260261#### Imported: Quick Reference262263### 1. Accessibility (CRITICAL)264265- `color-contrast` - Minimum 4.5:1 ratio for normal text266- `focus-states` - Visible focus rings on interactive elements267- `alt-text` - Descriptive alt text for meaningful images268- `aria-labels` - aria-label for icon-only buttons269- `keyboard-nav` - Tab order matches visual order270- `form-labels` - Use label with for attribute271272### 2. Touch & Interaction (CRITICAL)273274- `touch-target-size` - Minimum 44x44px touch targets275- `hover-vs-tap` - Use click/tap for primary interactions276- `loading-buttons` - Disable button during async operations277- `error-feedback` - Clear error messages near problem278- `cursor-pointer` - Add cursor-pointer to clickable elements279280### 3. Performance (HIGH)281282- `image-optimization` - Use WebP, srcset, lazy loading283- `reduced-motion` - Check prefers-reduced-motion284- `content-jumping` - Reserve space for async content285286### 4. Layout & Responsive (HIGH)287288- `viewport-meta` - width=device-width initial-scale=1289- `readable-font-size` - Minimum 16px body text on mobile290- `horizontal-scroll` - Ensure content fits viewport width291- `z-index-management` - Define z-index scale (10, 20, 30, 50)292293### 5. Typography & Color (MEDIUM)294295- `line-height` - Use 1.5-1.75 for body text296- `line-length` - Limit to 65-75 characters per line297- `font-pairing` - Match heading/body font personalities298299### 6. Animation (MEDIUM)300301- `duration-timing` - Use 150-300ms for micro-interactions302- `transform-performance` - Use transform/opacity, not width/height303- `loading-states` - Skeleton screens or spinners304305### 7. Style Selection (MEDIUM)306307- `style-match` - Match style to product type308- `consistency` - Use same style across all pages309- `no-emoji-icons` - Use SVG icons, not emojis310311### 8. Charts & Data (LOW)312313- `chart-type` - Match chart type to data type314- `color-guidance` - Use accessible color palettes315- `data-table` - Provide table alternative for accessibility316317#### Imported: Search Reference318319### Available Domains320321| Domain | Use For | Example Keywords |322|--------|---------|------------------|323| `product` | Product type recommendations | SaaS, e-commerce, portfolio, healthcare, beauty, service |324| `style` | UI styles, colors, effects | glassmorphism, minimalism, dark mode, brutalism |325| `typography` | Font pairings, Google Fonts | elegant, playful, professional, modern |326| `color` | Color palettes by product type | saas, ecommerce, healthcare, beauty, fintech, service |327| `landing` | Page structure, CTA strategies | hero, hero-centric, testimonial, pricing, social-proof |328| `chart` | Chart types, library recommendations | trend, comparison, timeline, funnel, pie |329| `ux` | Best practices, anti-patterns | animation, accessibility, z-index, loading |330| `react` | React/Next.js performance | waterfall, bundle, suspense, memo, rerender, cache |331| `web` | Web interface guidelines | aria, focus, keyboard, semantic, virtualize |332| `prompt` | AI prompts, CSS keywords | (style name) |333334### Available Stacks335336| Stack | Focus |337|-------|-------|338| `html-tailwind` | Tailwind utilities, responsive, a11y (DEFAULT) |339| `react` | State, hooks, performance, patterns |340| `nextjs` | SSR, routing, images, API routes |341| `vue` | Composition API, Pinia, Vue Router |342| `svelte` | Runes, stores, SvelteKit |343| `swiftui` | Views, State, Navigation, Animation |344| `react-native` | Components, Navigation, Lists |345| `flutter` | Widgets, State, Layout, Theming |346| `shadcn` | shadcn/ui components, theming, forms, patterns |347348---349350#### Imported: Prerequisites351352Check if Python is installed:353354```bash355python3 --version || python --version356```357358If Python is not installed, install it based on user's OS:359360**macOS:**361```bash362brew install python3363```364365**Ubuntu/Debian:**366```bash367sudo apt update && sudo apt install python3368```369370**Windows:**371```powershell372winget install Python.Python.3.12373```374375---376377#### Imported: How to Use This Skill378379When user requests UI/UX work (design, build, create, implement, review, fix, improve), follow this workflow:380381### Step 1: Analyze User Requirements382383Extract key information from user request:384- **Product type**: SaaS, e-commerce, portfolio, dashboard, landing page, etc.385- **Style keywords**: minimal, playful, professional, elegant, dark mode, etc.386- **Industry**: healthcare, fintech, gaming, education, etc.387- **Stack**: React, Vue, Next.js, or default to `html-tailwind`388389### Step 2: Generate Design System (REQUIRED)390391**Always start with `--design-system`** to get comprehensive recommendations with reasoning:392393```bash394python3 .claude/skills/ui-ux-pro-max/scripts/search.py "<product_type> <industry> <keywords>" --design-system [-p "Project Name"]395```396397This command:3981. Searches 5 domains in parallel (product, style, color, landing, typography)3992. Applies reasoning rules from `ui-reasoning.csv` to select best matches4003. Returns complete design system: pattern, style, colors, typography, effects4014. Includes anti-patterns to avoid402403**Example:**404```bash405python3 .claude/skills/ui-ux-pro-max/scripts/search.py "beauty spa wellness service" --design-system -p "Serenity Spa"406```407408### Step 3: Supplement with Detailed Searches (as needed)409410After getting the design system, use domain searches to get additional details:411412```bash413python3 .claude/skills/ui-ux-pro-max/scripts/search.py "<keyword>" --domain <domain> [-n <max_results>]414```415416**When to use detailed searches:**417418| Need | Domain | Example |419|------|--------|---------|420| More style options | `style` | `--domain style "glassmorphism dark"` |421| Chart recommendations | `chart` | `--domain chart "real-time dashboard"` |422| UX best practices | `ux` | `--domain ux "animation accessibility"` |423| Alternative fonts | `typography` | `--domain typography "elegant luxury"` |424| Landing structure | `landing` | `--domain landing "hero social-proof"` |425426### Step 4: Stack Guidelines (Default: html-tailwind)427428Get implementation-specific best practices. If user doesn't specify a stack, **default to `html-tailwind`**.429430```bash431python3 .claude/skills/ui-ux-pro-max/scripts/search.py "<keyword>" --stack html-tailwind432```433434Available stacks: `html-tailwind`, `react`, `nextjs`, `vue`, `svelte`, `swiftui`, `react-native`, `flutter`, `shadcn`435436---437438#### Imported: Output Formats439440The `--design-system` flag supports two output formats:441442```bash443# ASCII box (default) - best for terminal display444python3 .claude/skills/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system445446# Markdown - best for documentation447python3 .claude/skills/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system -f markdown448```449450---451452#### Imported: Tips for Better Results4534541. **Be specific with keywords** - "healthcare SaaS dashboard" > "app"4552. **Search multiple times** - Different keywords reveal different insights4563. **Combine domains** - Style + Typography + Color = Complete design system4574. **Always check UX** - Search "animation", "z-index", "accessibility" for common issues4585. **Use stack flag** - Get implementation-specific best practices4596. **Iterate** - If first search doesn't match, try different keywords460461---462463#### Imported: Pre-Delivery Checklist464465Before delivering UI code, verify these items:466467### Visual Quality468- [ ] No emojis used as icons (use SVG instead)469- [ ] All icons from consistent icon set (Heroicons/Lucide)470- [ ] Brand logos are correct (verified from Simple Icons)471- [ ] Hover states don't cause layout shift472- [ ] Use theme colors directly (bg-primary) not var() wrapper473474### Interaction475- [ ] All clickable elements have `cursor-pointer`476- [ ] Hover states provide clear visual feedback477- [ ] Transitions are smooth (150-300ms)478- [ ] Focus states visible for keyboard navigation479480### Light/Dark Mode481- [ ] Light mode text has sufficient contrast (4.5:1 minimum)482- [ ] Glass/transparent elements visible in light mode483- [ ] Borders visible in both modes484- [ ] Test both modes before delivery485486### Layout487- [ ] Floating elements have proper spacing from edges488- [ ] No content hidden behind fixed navbars489- [ ] Responsive at 375px, 768px, 1024px, 1440px490- [ ] No horizontal scroll on mobile491492### Accessibility493- [ ] All images have alt text494- [ ] Form inputs have labels495- [ ] Color is not the only indicator496- [ ] `prefers-reduced-motion` respected497498### When to Use499This skill is applicable to execute the workflow or actions described in the overview.500501#### Imported: Limitations502503- Use this skill only when the task clearly matches the scope described above.504- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.505- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.