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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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 commands and concrete examples and has a clear sequenced decision flow, but it is long for a single skill, its validate-fix-retry loop is implicit, and several slide-system file references point to files that are absent from the bundle.

Suggestions

Move the large Slide System section into a dedicated reference file so SKILL.md stays a lean overview pointing one level deep.

Make the validation feedback loop explicit (validate → if errors, fix and re-validate → only then generate final HTML).

Either add the missing referenced files (data/*.csv, assets/design-tokens.json/.css, docs/brand-guidelines.md, the reference HTML) or remove/correct the dead references so all navigation targets exist.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient — tables, commands, and code blocks with no padded prose explaining concepts Claude already knows — but it runs ~240 lines spanning two large domains (design tokens plus a full slide-generation system), and the slide section could be split into a reference, so it could be tightened rather than being fully lean.	2 / 3
Actionability	It provides fully executable, copy-paste-ready commands ('node scripts/generate-tokens.cjs --config tokens.json -o tokens.css', 'python scripts/search-slides.py "investor pitch"') plus concrete CSS and Chart.js examples, matching the anchor for fully executable guidance with specific examples.	3 / 3
Workflow Clarity	The 'Contextual Decision Flow' gives a clear 1→5 sequence with an explicit validation step ('5. Validate with slide-token-validator.py') and a requirements checklist, but the validate→fix→retry feedback loop is implicit rather than spelled out, and a 'Pattern Breaking' section sits outside the main sequence, leaving checkpoints partially implicit.	2 / 3
Progressive Disclosure	There is a well-signaled References table pointing to 7 real one-level-deep files (all present) plus Scripts/Templates tables, but the Slide System references many paths (data/.csv, docs/brand-guidelines.md, assets/design-tokens.json, assets/designs/slides/.html) that do not exist in the bundle, so navigation is only partially trustworthy.	2 / 3
	Total	9 / 12 Passed

Description

77%

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 specific and complete with both a clear capability list and an explicit 'Use for' trigger clause, but its trigger-term coverage is partial and the slide-generation half risks overlap with separate presentation skills.

Suggestions

Add the natural terms users would say — 'design system', 'slides', 'presentations', 'theme' — to the 'Use for' clause to broaden trigger-term coverage.

Sharpen distinctiveness by stating what is unique (e.g. token-driven brand-compliant slides) so it does not collide with a generic presentation skill.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete capabilities — 'Token architecture, component specifications, and slide generation' and 'Three-layer tokens (primitive→semantic→component), CSS variables, spacing/typography scales, component specs, strategic slide creation' — matching the anchor for listing multiple specific concrete actions.	3 / 3
Completeness	It explicitly answers both 'what does this do' (token architecture, component specs, slide generation) and 'when should Claude use it' via the explicit 'Use for design tokens, systematic design, brand-compliant presentations' trigger clause.	3 / 3
Trigger Term Quality	It includes a 'Use for design tokens, systematic design, brand-compliant presentations' clause with some relevant keywords, but misses common natural variations users would actually say (e.g. 'design system', 'slides', 'presentation', 'theme'), so coverage is partial rather than comprehensive.	2 / 3
Distinctiveness Conflict Risk	The design-token niche is reasonably distinct, but bundling 'strategic slide creation' / 'brand-compliant presentations' could overlap with a dedicated presentation skill, and the term 'design system' itself is absent, so it remains only somewhat specific with potential overlap.	2 / 3
	Total	10 / 12 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
Commit: cc3d1be

Reviewed: 2 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.