CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

shadcn-customization

Shadcn/ui theming and component customization — CSS variables, OKLCH colors, dark mode, variants, wrappers. Load for any ticket involving colors, theme, UI layout, or component styling.

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A solid, dense reference: concrete commands, executable CSS/TSX examples, an ordered customization ladder, and Red Flags plus a Verification checklist. Weaknesses are minor — one non-compiling TSX example, a small amount of known-concept explanation, no error-recovery guidance, and a broken run-on sentence in the intro ("Components reference semantic CSS variable tokens change the variables to change every component").

Suggestions

Fix the broken intro sentence ("Components reference semantic CSS variable tokens change the variables to change every component") — it is ungrammatical and obscures the skill's core mental model.

Add TypeScript prop types to the ConfirmDialog wrapper example so it compiles in the strict-TS projects shadcn generates, or note that types are elided for brevity.

Trim the OKLCH anatomy parenthetical (lightness/chroma/hue ranges) — Claude already knows OKLCH — and spend the tokens on an error-recovery note instead, e.g., what to check when a preset apply conflicts with local component customizations.

DimensionReasoningScore

Conciseness

Dense, token-efficient format (variable table, short fenced examples, no padded prose), but a few tokens don't earn their place — e.g., the OKLCH anatomy explanation "lightness (0–1), chroma (0 = gray), and hue (0–360)" restates a concept Claude already knows, and the "How It Works" section is borderline. Not 5 for these trimmable spots; not 3 because there is no padded section or unnecessary tutorial framing.

4 / 5

Actionability

Mostly copy-paste-ready: concrete commands ("npx shadcn@latest apply --preset a2r6bw"), complete CSS registration blocks, and specific file paths ("src/components/admin/theme-provider.tsx"). Not 5 because the ConfirmDialog TSX snippet uses untyped destructured props, which won't compile under the strict TypeScript typical of shadcn projects — a minor executability gap.

4 / 5

Workflow Clarity

Clear sequences with most checkpoints present: an ordered decision ladder ("Prefer these approaches in order: 1. Built-in variants ... 4. Wrapper components"), a numbered 3-step custom-color workflow, plus Red Flags and a Verification checklist. Not 5 because there are no feedback/error-recovery loops (e.g., what to do if "apply --force" overwrites local customizations) and the custom-color workflow lacks inline validation.

4 / 5

Progressive Disclosure

Well-organized single-file skill with clear section headers and an explicit cross-skill pointer; no bundle files exist and none are needed for navigation. Not 5 because at ~190 lines (above the under-50-line simple-skill threshold) the full variable table and the customization ladder sit inline in one file with no signaled references, leaving minor organization headroom.

4 / 5

Total

16

/

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 description: it names a clear niche, lists concrete capability areas, and closes with an explicit trigger clause covering natural user terms. Its only weaknesses are noun-phrase rather than action-verb capability listing and slightly broad triggers ("UI layout") that could collide with a general frontend skill.

DimensionReasoningScore

Specificity

Names the domain precisely ("Shadcn/ui theming and component customization") and enumerates several concrete capability areas ("CSS variables, OKLCH colors, dark mode, variants, wrappers"), though these are noun topics rather than stated actions and coverage has minor gaps (e.g., presets, border radius).

4 / 5

Completeness

Explicitly answers both: what ("Shadcn/ui theming and component customization — CSS variables, OKLCH colors, dark mode, variants, wrappers") and when ("Load for any ticket involving colors, theme, UI layout, or component styling") with concrete trigger phrases. The "Load for any ticket involving..." clause is explicit trigger guidance equivalent to "Use when...", so the missing-trigger cap does not apply.

5 / 5

Trigger Term Quality

Includes natural terms users would say — "colors", "theme", "dark mode", "UI layout", "component styling" — but misses common variations like "Tailwind", "design tokens", or "brand colors". Not 5 because coverage of synonyms is not comprehensive; not 3 because multiple natural phrases are present.

4 / 5

Distinctiveness Conflict Risk

The shadcn/ui theming niche is clear, but the "UI layout" and "component styling" triggers are broad enough to overlap with a general frontend architecture skill (which the body itself cross-references). Not 5 due to this minor overlap risk with closely related skills.

4 / 5

Total

17

/

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

marmelab/atomic-crm

Path

.claude/skills/shadcn-customization/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.