ui-ux-pro-max
starsforks
How to install ui-ux-pro-max?
selmakcby/claude-agents-skills/ui-ux-pro-max
$npx -y skills add selmakcby/claude-agents-skills --skill ui-ux-pro-maxUI/UX design intelligence for web and mobile. Includes 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. Use when designing UI, choosing palettes, typography, or component ar
SKILL.md
| 1 | <!-- |
| 2 | Source: nextlevelbuilder/ui-ux-pro-max-skill |
| 3 | File: https://github.com/nextlevelbuilder/ui-ux-pro-max-skill/blob/main/.claude/skills/ui-ux-pro-max/SKILL.md |
| 4 | Install: npx uipro init --ai claude |
| 5 | Used by: ui-agent |
| 6 | --> |
| 7 | |
| 8 | # UI/UX Pro Max |
| 9 | |
| 10 | ## When to trigger |
| 11 | - User requests UI/UX design |
| 12 | - Keywords: "component", "layout", "design system", "color palette", "landing page", "dashboard" |
| 13 | - Any new visual surface |
| 14 | |
| 15 | ## Reference files |
| 16 | |
| 17 | This skill's folder contains searchable databases (loaded on demand): |
| 18 | |
| 19 | - `styles.md` — 50+ styles (glassmorphism, brutalism, neumorphism, bento grid, ...) |
| 20 | - `palettes.md` — 161 color palettes with HEX codes |
| 21 | - `fonts.md` — 57 font pairings (heading + body combos) |
| 22 | - `products.md` — 161 product types with reasoning rules |
| 23 | - `guidelines.md` — 99 UX guidelines |
| 24 | - `charts.md` — 25 chart types across stacks |
| 25 | |
| 26 | *(Stub files will be created as needed — see `styles.md` for example)* |
| 27 | |
| 28 | ## Supported stacks |
| 29 | |
| 30 | React · Next.js · Astro · Vue · Nuxt · Svelte · SwiftUI · React Native · Flutter · HTML+Tailwind (default) |
| 31 | |
| 32 | ## Design process |
| 33 | |
| 34 | ### 1. Understand the need |
| 35 | - What product type? (SaaS landing, dashboard, portfolio, ...) |
| 36 | - What audience? |
| 37 | - What tone? (serious / playful / technical / luxury) |
| 38 | |
| 39 | ### 2. Pick a style |
| 40 | Look up `styles.md` — pick one matching the product type + tone. |
| 41 | |
| 42 | ### 3. Pick a palette |
| 43 | Look up `palettes.md` — match brand identity. Pay attention to contrast for accessibility. |
| 44 | |
| 45 | ### 4. Pick typography |
| 46 | Look up `fonts.md` — pick a heading + body pair. Web-safe or Google Fonts preferred. |
| 47 | |
| 48 | ### 5. Component plan |
| 49 | - Layout (grid system, hero, sections) |
| 50 | - Components (reuse shadcn/ui where possible) |
| 51 | - Interaction states (hover, focus, loading, error) |
| 52 | |
| 53 | ### 6. Accessibility check |
| 54 | - Contrast ratio WCAG AA min |
| 55 | - Aria labels on interactive elements |
| 56 | - Keyboard navigation order |
| 57 | - Focus indicators visible |
| 58 | |
| 59 | ## Output format |
| 60 | |
| 61 | ```markdown |
| 62 | ## Design Summary |
| 63 | |
| 64 | **Product type:** <type> |
| 65 | **Style:** <name> — *reason for choice* |
| 66 | **Palette:** |
| 67 | - Primary: #HEX |
| 68 | - Secondary: #HEX |
| 69 | - Accent: #HEX |
| 70 | - Text: #HEX |
| 71 | - Background: #HEX |
| 72 | |
| 73 | **Typography:** |
| 74 | - Heading: <font> |
| 75 | - Body: <font> |
| 76 | - Mono: <font> |
| 77 | |
| 78 | **Layout:** |
| 79 | <grid/structure description or ASCII sketch> |
| 80 | |
| 81 | **Key components:** |
| 82 | - <Component> — <purpose> |
| 83 | |
| 84 | **Accessibility:** |
| 85 | - <aria notes> |
| 86 | - <keyboard nav> |
| 87 | - <contrast verified> |
| 88 | |
| 89 | **Responsive breakpoints:** |
| 90 | - Mobile: <behavior> |
| 91 | - Tablet: <behavior> |
| 92 | - Desktop: <behavior> |
| 93 | ``` |
| 94 | |
| 95 | ## Rules |
| 96 | |
| 97 | - Default stack: Tailwind v4 + shadcn/ui. |
| 98 | - Never introduce new design dependencies silently — flag as a decision. |
| 99 | - Reuse existing components before creating new ones. |
| 100 | - Dark mode + responsive by default. |
| 101 | - Accessibility is mandatory — every component gets aria + keyboard nav. |
| 102 | - Never write implementation code — produce a brief, builder codes from it. |
People who liked this also viewed
6 picksType
- web-design-guidelinesReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".SkillsJul 2026
- lark-slides飞书幻灯片：创建和编辑幻灯片。创建演示文稿、读取幻灯片内容、管理幻灯片页面（创建、删除、读取、局部替换）。当用户需要创建或编辑幻灯片、读取或修改单个页面时使用。当用户给出 doubao.com 的 /slides/ URL/token 时，也应直接使用本 skill，不要因为域名不是飞书而回退到 WebFetch；路由依据是 URL 路径模式和 token，而不是域名。不负责：云文档内容编辑（走 SkillsJul 2026
- design-taste-frontendTaste-Skill - gives your AI good taste. stops the AI from generating boring, generic slop SkillsJul 2026
- ui-ux-pro-maxUI/UX design intelligence for web and mobile. Searchable local database with 84 styles, 192 color palettes, 74 font pairings, 192 product types, 98 UX guidelines, 104 icon entries, 16 GSAP motion presSkillsJul 2026
- caveman-helpQuick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".SkillsJul 2026
- codebase-designShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-nSkillsJul 2026
