CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ui-design-system

React UI component systems with TailwindCSS + Radix + shadcn/ui. Stack: TailwindCSS (styling), Radix UI (primitives), shadcn/ui (components), React/Next.js. Capabilities: design system architecture, accessible components, responsive layouts, theming, dark mode, component composition. Actions: review, design, build, improve, refactor UI components. Keywords: TailwindCSS, Radix UI, shadcn/ui, design system, component library, accessibility, ARIA, responsive, dark mode, theming, CSS variables, component architecture, atomic design, design tokens, variant, slot, composition. Use when: building component libraries, implementing shadcn/ui, creating accessible UIs, setting up design systems, adding dark mode/theming, reviewing UI component architecture.

Quality

68%

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-design-system/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

38%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 well-organized for navigation with a real, correctly-linked reference bundle, but it reads as a padded capability brochure: heavy redundancy, re-explanations of well-known framework concepts, and almost no executable code or commands. Consolidating the duplicated summary sections and moving concept explanations into the existing references would substantially improve token efficiency and actionability.

Suggestions

Collapse the redundant catalog sections ('Core Capabilities', 'Triggers & Use Cases', 'Behavioral Traits', 'Response Approach', 'Skill Summary', 'Best Practices Summary') into one concise overview — the same facts currently appear 3-4 times across 470 lines.

Replace descriptive guidance with executable content: the actual shadcn/ui CLI install command, a working tailwind.config + globals.css pair, and a copy-paste component example, since only one small CSS snippet is currently executable.

Either link canvas-design-system.md from SKILL.md (and its anchor sections) or remove it from the bundle, and move the inline concept explanations (what each layer is, WCAG basics) into the corresponding reference files.

DimensionReasoningScore

Conciseness

The 470-line body is noticeably verbose: it re-explains concepts Claude already knows ("Utility-first CSS framework with build-time generation", "Unstyled, accessible component primitives", basic WCAG contrast ratios) and repeats the same capability/trigger lists three to four times across 'Core Capabilities', 'Triggers & Use Cases', 'Behavioral Traits', 'Skill Summary', and 'Best Practices Summary'. Not a 1 because there are pockets of genuinely non-obvious specifics (three-tier token snippet, contrast thresholds, config pointers).

2 / 5

Actionability

Concrete executable guidance is minimal: one CSS-variables snippet and scattered specifics (contrast ratios, breakpoint names), but no install commands ("shadcn/ui CLI" is named without the command), no component code, and no executable review procedure — most sections are descriptive bullet catalogs like "Use Tailwind's design system consistently" and "Configure @/components in tsconfig". It sits above the entirely-vague anchor because a few values are actionable.

2 / 5

Workflow Clarity

Sequences exist (Installation Order 1-5, Review/Design/Improve phase flows in 'Response Approach', and implementation checklists), so a rough order is clear. Validation is only implicit — checklist items like 'Test accessibility' and 'Verify WCAG AA contrast' name checks but no feedback loops, error-recovery steps, or explicit checkpoints, matching the 'steps listed but validation gaps' anchor rather than the checkpoint-rich one above.

3 / 5

Progressive Disclosure

References are one level deep and clearly signaled ('See DESIGN_TOKENS.md for: ...' with per-file bullet lists), and all referenced anchors resolve in the real bundle files. Not a 5 because SKILL.md itself inlines large catalog sections that belong in the reference files, and the bundle file canvas-design-system.md is never referenced from SKILL.md, leaving a discovery gap.

4 / 5

Total

11

/

20

Passed

Description

83%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.

A strong, explicit description that clearly states capabilities, stack, keywords, and 'Use when' triggers, with good distinctiveness. Its main weakness is keyword-stuffing that pads length and mixes natural trigger phrases with internal jargon.

Suggestions

Trim the raw keyword dump ('Keywords: ... variant, slot, composition') and fold the genuinely natural trigger phrases into the prose, since verbosity is penalized and jargon terms users would not say dilute trigger quality.

Clarify the boundary with adjacent React skills in the 'Use when' clause (e.g., exclude React architecture/state management) to reduce overlap risk with a react-nextjs-expert-style skill.

DimensionReasoningScore

Specificity

The description lists several concrete actions ("review, design, build, improve, refactor UI components") plus a capability list ("design system architecture, accessible components, responsive layouts, theming, dark mode"), giving specific coverage of the domain with only minor gaps. It falls short of a 5 because the actions are generic verbs made concrete only by the domain nouns, not operations as tangible as 'extract text and tables'.

4 / 5

Completeness

It explicitly answers 'what' ("design system architecture, accessible components, responsive layouts, theming, dark mode, component composition") and 'when' with a concrete 'Use when:' clause ("building component libraries, implementing shadcn/ui, creating accessible UIs, setting up design systems, adding dark mode/theming, reviewing UI component architecture"), matching the top anchor exactly.

5 / 5

Trigger Term Quality

Good keyword coverage including natural user phrases like "design system", "component library", "accessibility", "dark mode", "theming", "responsive", alongside stack names (TailwindCSS, Radix UI, shadcn/ui). Not a 5 because entries like "variant", "slot", "composition" are jargon users would rarely say, and the terms are packed into a keyword dump rather than natural phrasing.

4 / 5

Distinctiveness Conflict Risk

The TailwindCSS + Radix + shadcn/ui niche is clear and triggers are scoped, so conflict risk is low. Minor overlap remains with a general React/Next.js skill since "React/Next.js" appears in the stack clause and several triggers (responsive layouts, component composition) could fire for adjacent skills.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

samhvw8/dot-claude

Path

skills/ui-design-system/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.