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.

1.37x

Quality

67%

Does it follow best practices?

Impact

74%

1.37x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/data/0-ui-ux-pro-max/SKILL.md

Quality

Discovery

57%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description excels at listing comprehensive capabilities with excellent trigger term coverage across frameworks, design styles, and UI elements. However, it critically lacks any explicit 'Use when...' guidance, making it difficult for Claude to know when to select this skill over others. The description reads as a feature dump rather than actionable selection criteria.

Suggestions

Add an explicit 'Use when...' clause specifying trigger conditions, e.g., 'Use when the user asks about UI/UX design, styling components, choosing color palettes, or implementing visual designs in web/mobile frameworks.'

Consolidate the keyword lists and add context about when this skill should be chosen over general coding skills, e.g., 'Select this skill for design-focused tasks rather than pure logic or backend work.'

Consider restructuring to lead with the purpose statement before the capability lists to improve scannability for skill selection.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions (plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check) and detailed elements (button, modal, navbar, sidebar, card, table, form, chart) with specific styles and frameworks.	3 / 3
Completeness	While the 'what' is extensively covered with actions, elements, and styles, there is no explicit 'Use when...' clause or equivalent trigger guidance explaining when Claude should select this skill. The description is purely a capability list without selection criteria.	1 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: project types (website, landing page, dashboard, mobile app), file extensions (.html, .tsx, .vue, .svelte), UI elements (button, modal, navbar), design styles (glassmorphism, dark mode, responsive), and frameworks (React, Next.js, Vue, Tailwind, shadcn/ui).	3 / 3
Distinctiveness Conflict Risk	The UI/UX focus with specific design styles (glassmorphism, neumorphism, bento grid) provides some distinctiveness, but the broad coverage of multiple frameworks and generic actions like 'build, create, design' could overlap with general web development or framework-specific skills.	2 / 3
	Total	9 / 12 Passed

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. Its main weakness is length—it includes setup instructions Claude doesn't need and inline reference tables that could be externalized. The pre-delivery checklist and hierarchical design system pattern are excellent additions that demonstrate thoughtful workflow design.

Suggestions

Remove Python installation instructions—Claude knows how to install Python and can determine the user's OS contextually

Move the detailed reference tables (Available Domains, Available Stacks, Common Rules) to separate reference files and link to them from the main skill

Consolidate the 'Quick Reference' and 'Common Rules for Professional UI' sections which have overlapping content about accessibility and interaction patterns

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 setup steps and consolidating similar sections.	2 / 3
Actionability	Provides fully executable bash commands with concrete examples, specific flag combinations, and copy-paste ready code. The workflow steps are explicit with real command examples like `python3 skills/ui-ux-pro-max/scripts/search.py "beauty spa wellness service" --design-system -p "Serenity Spa"`.	3 / 3
Workflow Clarity	Clear 4-step workflow with explicit sequencing (Analyze → Generate Design System → Supplement → Stack Guidelines). Includes validation through the pre-delivery checklist with checkboxes, and the hierarchical retrieval pattern provides clear decision logic for page-specific overrides.	3 / 3
Progressive Disclosure	Content is well-structured with clear sections and tables, but the document is quite long (~400 lines) with detailed reference tables that could be split into separate files. The skill mentions external files (ui-reasoning.csv, MASTER.md) but doesn't clearly signal what content lives where upfront.	2 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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.

Repository: majiayu000/claude-skill-registry
Commit: 6213d1a

Reviewed: about 4 hours ago

Table of Contents

Discovery Implementation Validation

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.