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.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Instruções da origem · Visualização somente leitura
name
ui-ux-pro-max-v3
description
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.
This public intake copy packages plugins/antigravity-bundle-web-designer/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"
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
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-v3 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-v3 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-v3 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-v3 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-bundle-web-designer/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
@3d-web-experience-v3 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@canvas-design-v4 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@form-cro-v3 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@frontend-design-v5 - 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
