ui-ux-pro-max
UI/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.
Install with Tessl CLI
npx tessl i github:nextlevelbuilder/ui-ux-pro-max-skill --skill ui-ux-pro-max82
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with clear workflows and executable commands. The main weakness is verbosity—it includes content Claude already knows (Python installation) and inline reference material that could be externalized. The pre-delivery checklist and common rules sections add significant value but contribute to document length.
Suggestions
Remove Python installation instructions—Claude knows how to install Python and can determine the user's OS
Move 'Common Rules for Professional UI' and 'Pre-Delivery Checklist' to separate reference files (e.g., RULES.md, CHECKLIST.md) and link to them
Consolidate the 'Available Domains' and 'Available Stacks' tables into a single reference file to reduce main document length
| 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 removing obvious instructions. | 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 quite long (~300 lines) with detailed reference tables that could be split into separate files. The 'Common Rules' and 'Pre-Delivery Checklist' sections could be external references. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.