design-system

Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing/typography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/design-system/SKILL.md

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 well-structured, actionable skill body that balances inline code/commands with reference pointers. The main weaknesses are missing validate-fix-retry feedback loops and a slide section that references asset/data files not present in the bundle.

Suggestions

Add an explicit validate-fix-retry feedback loop to the Contextual Decision Flow (e.g., 'If slide-token-validator.py reports hardcoded values, fix the var() usage and re-validate before proceeding').

Either ship the referenced assets/data/templates (design-tokens.css, slide-strategies.csv, etc.) or move the detailed Slide System content into a reference file so SKILL.md stays an overview.

Trim concept-explaining asides like the Duarte Sparkline explanation and theme-switching best-practice note to assume Claude's competence and tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is dense and mostly actionable (commands, code, tables, decision flows), with only minor over-explanation such as the "Best Practices" theme-switching note and the "Pattern Breaking (Duarte Sparkline)" concept aside.	4 / 5
Actionability	Provides copy-paste-ready commands (generate-tokens.cjs, search-slides.py) and a complete Chart.js snippet, but the decision flow is somewhat abstract and references data/asset files that do not exist in the bundle, leaving minor gaps.	4 / 5
Workflow Clarity	The Contextual Decision Flow is a clearly numbered sequence that includes a validation step ("5. Validate with slide-token-validator.py"), but it lacks an explicit validate-fix-retry feedback loop, which is the gap that keeps it below 5.	4 / 5
Progressive Disclosure	Good structure with clearly signaled one-level-deep reference tables for tokens and scripts (all of which exist), but the large inlined Slide System section and references to non-existent assets/data/templates files are minor organization gaps.	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, concrete description that explicitly answers both what and when with a clear "Use for" clause. It is held back from a perfect score by noun-phrase rather than verb-driven capabilities and minor overlap risk from covering two distinct domains.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities ("Token architecture, component specifications, and slide generation", "CSS variables, spacing/typography scales, component specs, strategic slide creation") but they are noun-phrase capabilities rather than verb-driven actions, leaving minor gaps versus the fully concrete anchor 5.	4 / 5
Completeness	Clearly states both what (token architecture, component specs, slide generation with three-layer detail) and when ("Use for design tokens, systematic design, brand-compliant presentations") with concrete trigger phrases, matching the anchor 5 pattern.	5 / 5
Trigger Term Quality	The "Use for design tokens, systematic design, brand-compliant presentations" clause gives good keyword coverage with the natural term "design tokens", though common synonyms like "design system", "theme", or "Tailwind" are missing.	4 / 5
Distinctiveness Conflict Risk	It occupies a clear design-systems niche with distinct triggers, but bundling both token architecture and slide generation creates minor overlap risk with closely related skills (the body itself lists brand and ui-styling as dependencies).	4 / 5
	Total	17 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 5 missing, 2 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: nextlevelbuilder/ui-ux-pro-max-skill
Path: .claude/skills/design-system/SKILL.md
Commit: abb7f2f

Reviewed: 3 days 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.