ui-ux-pro-max
UI/UX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, and HTML/CSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, and flat design. Topics: color systems, accessibility, animation, layout, typography, font pairing, spacing, interaction states, shadow, and gradient. Integrations: shadcn/ui MCP for component search and examples.
74
68%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/ui-ux-pro-max/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a highly detailed and specific skill description that excels at enumerating concrete capabilities, trigger terms, and its distinct design-focused niche. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know precisely when to select this skill over others. The quantified data points (50+ styles, 161 palettes, etc.) add credibility but the description could benefit from a concise trigger statement.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to design, build, review, or improve UI/UX for web or mobile applications, or mentions design styles, color palettes, font pairings, or component styling.'
Consider slightly condensing the enumerated lists to reduce verbosity while preserving key trigger terms, and use the freed space for the 'Use when' guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists extensive concrete actions (plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check), specific project types, UI elements, design styles, and topics. It goes well beyond naming a domain and provides highly specific capabilities with quantified data (50+ styles, 161 color palettes, etc.). | 3 / 3 |
Completeness | The description thoroughly answers 'what does this do' with extensive capability listings, but it lacks an explicit 'Use when...' clause or equivalent trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'website', 'landing page', 'dashboard', 'button', 'modal', 'navbar', 'dark mode', 'responsive', 'glassmorphism', 'color', 'accessibility', 'typography', 'font pairing', 'React', 'Tailwind', 'shadcn/ui', 'mobile app', 'e-commerce', 'SaaS'. These are highly natural keywords that match real user requests. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a very clear niche around UI/UX design intelligence with specific design styles, color palettes, font pairings, and named technology stacks. The combination of design-specific vocabulary (glassmorphism, neumorphism, bento grid) and UI element specificity makes it highly unlikely to conflict with non-design skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
55%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides excellent actionability with concrete CLI commands and a clear workflow, but is severely undermined by its extreme verbosity. Hundreds of inline UX rules, style guidelines, and checklist items that Claude largely already knows consume enormous token budget. The content would be dramatically improved by moving reference tables to separate files and keeping SKILL.md as a lean overview with navigation pointers.
Suggestions
Move the Quick Reference sections (§1-§10 with 99+ rules) to a separate REFERENCE.md file and link to it, keeping only the priority table in SKILL.md
Move the 'Common Rules for Professional UI' tables and 'Pre-Delivery Checklist' to separate files (e.g., RULES.md, CHECKLIST.md) since these are reference material, not workflow instructions
Remove the 'When to Apply' section's obvious Skip criteria and verbose explanations - Claude can infer when UI/UX guidance is irrelevant
Eliminate redundancy between Quick Reference rules and Common Rules tables which cover overlapping topics (touch targets, contrast, icons, animation timing)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 500+ lines. Contains massive inline reference tables (99 UX guidelines, 25+ chart rules, etc.) that should be in separate files. The 'When to Apply' section explains obvious decision criteria Claude can infer. Repeats information across Quick Reference, Common Rules, and Pre-Delivery Checklist sections. Much of this is general UI/UX knowledge Claude already possesses. | 1 / 3 |
Actionability | Provides fully executable CLI commands with concrete examples, specific flag usage, and real query strings. The workflow steps are copy-paste ready with exact bash commands. The design system generation, domain searches, and stack guidelines all have concrete, runnable examples. | 3 / 3 |
Workflow Clarity | Clear 4-step workflow (Analyze → Design System → Detailed Searches → Stack Guidelines) with explicit sequencing. The scenario table maps user intents to specific starting steps. The 'Step 2 is REQUIRED' emphasis and the hierarchical retrieval pattern (Master + Overrides) provide clear validation logic. The pre-delivery checklist serves as a verification checkpoint. | 3 / 3 |
Progressive Disclosure | This is a monolithic wall of text. The Quick Reference section alone contains ~200 rules inline that should be in separate reference files. The Common Rules tables, Pre-Delivery Checklist, and detailed domain tables are all inlined rather than referenced. The skill mentions scripts and CSV files exist but dumps all reference content directly into the SKILL.md instead of linking to them. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (659 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- nextlevelbuilder/ui-ux-pro-max-skill
- Commit
4255c21
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.