
Ui Ux Pro Max
Give your coding agent structured UI/UX intelligence—palettes, typography, patterns, and stack-specific guidance—when you ship web or mobile interfaces without a dedicated designer.
Overview
UI/UX Pro Max is an agent skill most often used in Build (also Validate and Ship) that supplies searchable UI/UX design intelligence—styles, color and type systems, UX rules, and stack-specific guidance—for planning, imp
Install
npx skills add https://github.com/nextlevelbuilder/ui-ux-pro-max-skill --skill ui-ux-pro-maxWhat is this skill?
- Searchable design intelligence: 50+ styles, 161 palettes, font pairings, UX guidelines, and chart types with priority-ba
- Multi-stack coverage from HTML/CSS through React, Next.js, Vue, Svelte, Tailwind, shadcn/ui, React Native, Flutter, and
- Supports plan-through-check actions—design, implement, refactor, optimize, and review UI/UX—including optional shadcn/ui
Adoption & trust: 206k installs on skills.sh; 88.7k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are coding UI alone and lack a repeatable way to choose styles, colors, typography, and interaction patterns that feel intentional and accessible across your stack.
Who is it for?
Solo builders shipping SaaS dashboards, landing pages, or mobile apps who want agent-driven design decisions backed by a broad pattern library rather than one-off aesthetic guesses.
Skip if: Teams that already maintain a locked design system and only need pixel-perfect Figma handoff, or backend-only work with no UI surface.
When should I use this skill?
Invoke when the task involves UI structure, visual design decisions, interaction patterns, or user experience quality control—including plan, design, implement, review, fix, or optimize work on web or mobile UI.
What do I get? / Deliverables
You get priority-based design recommendations and actionable UI/UX guidance your agent can apply while planning, building, refactoring, or reviewing interface code.
- Stack-aligned UI/UX recommendations for styles, color, typography, layout, and interaction states
- Refactored or improved interface code guided by the skill’s UX guidelines
- Review notes targeting accessibility, animation, spacing, and component patterns
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Most installs happen while implementing screens and components, so the canonical shelf is Build; the skill is still invoked earlier for landing/prototype look-and-feel and later for UX review passes. Frontend is where structure, styling, interaction states, and component choices (including shadcn/ui) are decided and coded, matching the skill’s searchable stacks and element-level coverage.
Where it fits
Choose palette, typography, and layout patterns before you commit HTML for a waitlist landing page.
Apply product-type and style reasoning rules while scaffolding a clickable demo that still looks credible to early users.
Implement cards, tables, forms, and charts on a Next.js dashboard with stack-specific spacing, states, and component guidance.
Run a structured UX and accessibility pass on modals, nav, and forms before you tag a release.
Align hero layout, contrast, and mobile responsiveness on a marketing site you are about to share publicly.
How it compares
Use this as a design-intelligence skill package for structured UI decisions, not as an MCP server or a generic “pick random colors” chat prompt.
Common Questions / FAQ
Who is ui-ux-pro-max for?
It is for solo and indie builders using Claude Code, Cursor, Codex, or similar agents who own product UI and want stack-aware guidance on layout, visual style, typography, accessibility, and UX quality.
When should I use ui-ux-pro-max?
Use it whenever the task involves UI structure, visual design, interaction patterns, or UX review—in Build while implementing frontend or mobile UI, in Validate while designing a landing page or prototype, and in Ship while fixing or optimizing UX before release.
Is ui-ux-pro-max safe to install?
Treat it like any third-party skill: review what it can access in your environment and check the Security Audits panel on this Prism detail page before enabling it in production repos.
SKILL.md
READMESKILL.md - Ui Ux Pro Max
# UI/UX Pro Max - Design Intelligence Comprehensive design guide for web and mobile applications. Contains 50+ styles, 161 color palettes, 57 font pairings, 161 product types with reasoning rules, 99 UX guidelines, and 25 chart types across 10 technology stacks. Searchable database with priority-based recommendations. ## When to Apply This Skill should be used when the task involves **UI structure, visual design decisions, interaction patterns, or user experience quality control**. ### Must Use This Skill must be invoked in the following situations: - Designing new pages (Landing Page, Dashboard, Admin, SaaS, Mobile App) - Creating or refactoring UI components (buttons, modals, forms, tables, charts, etc.) - Choosing color schemes, typography systems, spacing standards, or layout systems - Reviewing UI code for user experience, accessibility, or visual consistency - Implementing navigation structures, animations, or responsive behavior - Making product-level design decisions (style, information hierarchy, brand expression) - Improving perceived quality, clarity, or usability of interfaces ### Recommended This Skill is recommended in the following situations: - UI looks "not professional enough" but the reason is unclear - Receiving feedback on usability or experience - Pre-launch UI quality optimization - Aligning cross-platform design (Web / iOS / Android) - Building design systems or reusable component libraries ### Skip This Skill is not needed in the following situations: - Pure backend logic development - Only involving API or database design - Performance optimization unrelated to the interface - Infrastructure or DevOps work - Non-visual scripts or automation tasks **Decision criteria**: If the task will change how a feature **looks, feels, moves, or is interacted with**, this Skill should be used. ## Rule Categories by Priority *For human/AI reference: follow priority 1→10 to decide which rule category to focus on first; use `--domain <Domain>` to query details when needed. Scripts do not read this table.* | Priority | Category | Impact | Domain | Key Checks (Must Have) | Anti-Patterns (Avoid) | |----------|----------|--------|--------|------------------------|------------------------| | 1 | Accessibility | CRITICAL | `ux` | Contrast 4.5:1, Alt text, Keyboard nav, Aria-labels | Removing focus rings, Icon-only buttons without labels | | 2 | Touch & Interaction | CRITICAL | `ux` | Min size 44×44px, 8px+ spacing, Loading feedback | Reliance on hover only, Instant state changes (0ms) | | 3 | Performance | HIGH | `ux` | WebP/AVIF, Lazy loading, Reserve space (CLS < 0.1) | Layout thrashing, Cumulative Layout Shift | | 4 | Style Selection | HIGH | `style`, `product` | Match product type, Consistency, SVG icons (no emoji) | Mixing flat & skeuomorphic randomly, Emoji as icons | | 5 | Layout & Responsive | HIGH | `ux` | Mobile-first breakpoints, Viewport meta, No horizontal scroll | Horizontal scroll, Fixed px container widths, Disable zoom | | 6 | Typography & Color |