ui-ux-pro-max
tessl i github:nextlevelbuilder/ui-ux-pro-max-skill --skill ui-ux-pro-maxUI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
Validation
81%| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
Implementation
77%This is a well-structured, highly actionable skill with clear workflows and executable commands. Its main weakness is verbosity—Python installation instructions and some explanatory text are unnecessary for Claude. The monolithic structure could benefit from splitting detailed reference sections into separate files.
Suggestions
Remove Python installation instructions—Claude knows how to install Python or can infer it from context
Move 'Common Rules for Professional UI' and 'Pre-Delivery Checklist' to separate reference files (e.g., CHECKLIST.md, COMMON-RULES.md) and link from main skill
Condense the 'Search Reference' tables—the domain/stack descriptions repeat information Claude can infer from examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., Python installation instructions Claude knows, repeated explanations of the workflow). The quick reference tables are efficient, but the document could be tightened by ~30% without losing value. | 2 / 3 |
Actionability | Provides fully executable bash commands with concrete examples, clear flag usage, and copy-paste ready code. The workflow steps are specific with exact command syntax and expected outputs. | 3 / 3 |
Workflow Clarity | Clear 4-step workflow with explicit sequencing (Analyze → Generate Design System → Supplement → Stack Guidelines). Includes validation via pre-delivery checklist and hierarchical retrieval pattern with clear decision logic. | 3 / 3 |
Progressive Disclosure | Content is well-structured with tables and sections, but the document is monolithic (~400 lines) with no references to external files. The 'Common Rules' and 'Pre-Delivery Checklist' sections could be separate files for better organization. | 2 / 3 |
Total | 10 / 12 Passed |
Activation
N/ASomething went wrong
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.