CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ui-ux-design

UI/UX design reference database. 50+ styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). 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.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ui-ux-design/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

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

The body is a well-structured orchestration guide: it delegates the bulk reference data to an on-demand search script, documents domains and stacks in scannable tables, sequences the workflow clearly, and includes an unusually valuable set of concrete do/don't rules and a pre-delivery checklist. Its main weaknesses are the padded Python-install prerequisite section, a duplicative worked example, and a hardcoded script path that doesn't match the bundle layout. Trimming the prerequisites and fixing the path would move it toward excellent.

Suggestions

Delete the Prerequisites section (Python version check plus per-OS install instructions) — Claude already knows how to check for and install Python; at most keep a one-line note that search.py requires Python 3.

Replace the hardcoded path `.claude/skills/ui-ux-design/scripts/search.py` with the bundle-relative `scripts/search.py` (noting to adjust for install location), so the commands are executable directly from the skill bundle.

Condense the Example Workflow: it duplicates Step 2's recommended search order as eight separate bash commands — either shorten it to 2-3 representative commands or fold the keywords into the Step 2 domain list to remove the repetition.

DimensionReasoningScore

Conciseness

The domain/stack tables and Common Rules tables are dense and token-efficient, but the ~25-line Prerequisites section walks through installing Python per-OS ("brew install python3", "sudo apt update && sudo apt install python3", "winget install Python.Python.3.12") — something Claude already knows — and the Example Workflow bash block largely restates Step 2's recommended search order. This matches anchor 3 (mostly efficient with some unnecessary explanation); not 2 because the padding is localized to two sections rather than pervasive.

3 / 5

Actionability

Commands are concrete and executable: `python3 .claude/skills/ui-ux-design/scripts/search.py "<keyword>" --domain <domain> [-n <max_results>]`, with a domains table giving example keywords per domain, a stacks table, and a fully worked example. This fits anchor 4 (mostly executable with minor gaps); not 5 because the hardcoded `.claude/skills/ui-ux-design/...` path assumes an install location rather than the bundle-relative `scripts/search.py`, and the `data/` CSVs that `core.py` requires are not present in the bundle as packaged, so the commands are not guaranteed to run as-is.

4 / 5

Workflow Clarity

The three-step sequence (analyze requirements → search domains in a recommended 1-8 order → apply stack guidelines, defaulting to html-tailwind) is clearly laid out, with an explicit iteration feedback loop ("If first search doesn't match, try different keywords") and a Pre-Delivery Checklist serving as a verification checkpoint. This matches anchor 4 (clear sequence, most checkpoints present); not 5 because there is no guidance for handling script errors or failed checklist items (no explicit fix-and-recheck loop).

4 / 5

Progressive Disclosure

The bulk reference content (50+ styles, palettes, font pairings, chart types, stack guidelines) correctly lives outside SKILL.md and is loaded on demand via `scripts/search.py` — effectively one-level-deep, clearly signaled references navigable through the domains and stacks tables. This fits anchor 4 (good structure, content appropriately placed, minor organization gaps); not 5 because the body references the script via a hardcoded install path instead of the bundle-relative `scripts/search.py`, and the `data/` files the search depends on are not visible in the bundle, weakening navigation certainty.

4 / 5

Total

15

/

20

Passed

Description

65%Weight 40%Scale 1-5

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 has excellent trigger-term coverage (comprehensive natural keywords, synonyms, and file extensions) and a clear domain identity, but it lacks an explicit 'Use when...' clause and its "Actions:" list is generic verb padding rather than concrete skill capabilities. The generic action keywords also create overlap risk with general coding skills. Adding an explicit trigger clause and describing the actual lookup/search capability would lift it substantially.

Suggestions

Add an explicit 'Use when...' clause (e.g., "Use when the user asks to design, build, or restyle UI — landing pages, dashbars, components — or mentions styles like glassmorphism or dark mode") to convert the implicit keyword lists into explicit trigger guidance and raise completeness.

Replace the generic verb dump ("plan, build, create, design, implement, review, fix, improve...") with the skill's actual concrete capability, e.g., "Searches a curated database of UI/UX styles, color palettes, font pairings, chart types, and stack-specific guidelines" — this sharpens specificity and reduces conflict with general coding skills.

Trim the action keywords to UI/UX-specific tasks (design, restyle, theme, pick colors/fonts) so the skill does not compete with generic code-review/refactor skills on ".tsx" and "review, fix, improve, refactor" requests.

DimensionReasoningScore

Specificity

"UI/UX design reference database. 50+ styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks" names the domain and enumerates its contents concretely, but the "Actions:" list ("plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor") is a dump of generic verbs rather than skill-specific capabilities — it never states the skill searches/looks up patterns. This matches anchor 3 (clear domain, actions not comprehensive/specific); it is not 4 because the listed actions are not specific to this skill.

3 / 5

Completeness

The "what" is clear (a reference database with enumerated contents), but there is no "Use when..." clause or equivalent explicit trigger guidance — the Projects/Elements/Styles/Topics lists only weakly imply when to invoke it. Per the judging guideline capping completeness at 3 for a missing 'Use when...' clause, this matches anchor 3 ("clear 'what' but 'when' is missing or only weakly implied"); not 4 because no explicit 'when' statement exists at all.

3 / 5

Trigger Term Quality

The description achieves comprehensive natural-term coverage including synonyms and file extensions: "glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode", "button, modal, navbar, sidebar, card, table, form, chart", ".html, .tsx, .vue, .svelte", and "website, landing page, dashboard, e-commerce, SaaS, portfolio". This matches anchor 5 exactly; users would naturally say these phrases when needing UI design help.

5 / 5

Distinctiveness Conflict Risk

Style- and topic-specific terms ("glassmorphism", "bento grid", "color palette", "font pairing") establish a distinct niche, but the broad action verbs "review, fix, improve, optimize, enhance, refactor" combined with ".tsx" would trigger on nearly any frontend coding request, creating real overlap with general coding/refactoring skills. This fits anchor 3 (somewhat specific but could still overlap with similar skills); not 4 because the generic action list materially raises conflict risk.

3 / 5

Total

14

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

samhvw8/dot-claude

Path

skills/ui-ux-design/SKILL.md

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.