CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

80

1.37x
Quality

77%

Does it follow best practices?

Impact

74%

1.37x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./data/0-ui-ux-pro-max/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable CLI commands, a clear sequenced workflow, and validation checklists, scoring well on actionability and workflow clarity. It loses points for repetition/verbosity and critically for progressive disclosure, since the referenced scripts and CSV files are absent from the bundle and large reference content is inlined rather than split into real files.

Suggestions

Include the referenced bundle files (scripts/search.py and references/ui-reasoning.csv) so the documented commands actually work, or remove the references and document the data source instead.

Move the large rule tables (Quick Reference, Common Rules) into one-level-deep reference files (e.g., references/rules.md) and keep SKILL.md as a concise overview, improving progressive disclosure and token efficiency.

Remove the duplicated Python-install prerequisite walkthrough and the repeated design-system example, since the workflow is already shown once in 'How to Use This Skill'.

DimensionReasoningScore

Conciseness

Mostly efficient with tables and short rule lines, but repeats the prerequisite Python install walkthrough, duplicates the design-system workflow across 'How to Use' and 'Example Workflow', and re-lists quick-reference rules that the bundled CSV/CLI already provides.

2 / 3

Actionability

Provides concrete, copy-paste-ready CLI commands for every step (e.g., 'python3 skills/ui-ux-pro-max/scripts/search.py ... --design-system -p "Serenity Spa"') with worked examples and explicit default-stack guidance.

3 / 3

Workflow Clarity

Multi-step process is clearly sequenced (Analyze -> Generate design system -> Supplement -> Stack guidelines) with explicit REQUIRED markers, a persist/override sub-pattern, and a pre-delivery checklist serving as validation checkpoints.

3 / 3

Progressive Disclosure

The skill body references bundled files (search.py, ui-reasoning.csv) but ./scripts and ./references do not exist in the bundle, so referenced paths are broken; the SKILL.md also inlines large rule tables instead of pointing one level deep to real reference files.

1 / 3

Total

9

/

12

Passed

Description

87%

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 is information-dense, naming concrete actions, artifacts, styles, and stacks, which drives strong specificity and trigger-term coverage. Its main weakness is the absence of an explicit 'Use when...' trigger clause and the broad action-verb list that raises conflict risk with general coding skills.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when designing or building UI/UX for web or mobile apps') to make the trigger unambiguous and satisfy the completeness anchor fully.

Trim the generic action verbs ('plan, build, create, fix, improve') and scope them to UI/UX so the description is less likely to conflict with general coding skills.

The description is third-person and specific, which is good; keep it but consider reducing the long comma-separated lists slightly to aid scannability.

DimensionReasoningScore

Specificity

Lists many concrete actions ('plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code') and concrete artifacts across stacks, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Answers 'what' via enumerated actions/elements/styles and implies 'when' through trigger verbs and project types, though it lacks an explicit 'Use when...' clause; the verb list functions as a clear trigger.

3 / 3

Trigger Term Quality

Densely packs natural user terms — 'website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx', plus style and element names users actually say, giving good coverage.

3 / 3

Distinctiveness Conflict Risk

The niche (UI/UX design intelligence across 9 stacks) is fairly distinct, but the breadth of generic action verbs (plan, build, create, fix, improve) could overlap with many general coding skills and trigger for the wrong skill.

2 / 3

Total

11

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
majiayu000/claude-skill-registry-data
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.