CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

design-system-builder

Builds and evolves enterprise-quality CSS Design Systems based on Chameleon web components. Use when the user wants to create, scaffold, or evolve a DS, add components/tokens/themes. Triggers on: 'design system', 'DS', 'design tokens', 'theme system', 'build a DS', 'scaffold DS', 'create design system'.

Quality

84%

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

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

An exceptionally actionable, well-sequenced skill with a strong reference architecture — every referenced file exists and navigation is easy. The main weakness is token efficiency: substantial rule duplication between the Phase 4b audit and Key Rules, plus inline reference-grade material.

Suggestions

Consolidate the ::part(), :disabled, no-DS-prefix, and no-em/rem rules that currently appear in both Phase 4b and Key Rules into a single canonical location (e.g., keep the audit checklist in Phase 4b and have Key Rules link to it) to cut duplicated tokens.

Move the 10-row Chameleon component inventory table into a reference file (e.g., references/component-catalog.md) and keep only the decision rule ("exists in Chameleon → CSS only; not exists → offer Kasstor") in SKILL.md.

Replace the 25-line inner-skill directory tree in Phase 6 with a link to references/inner-skill-pattern.md, which already documents the structure, retaining only the required-contents list.

DimensionReasoningScore

Conciseness

Mostly efficient, project-specific content, but noticeably duplicated: the ::part() combinator/pseudo-element limits, :disabled preference, no-DS-name-prefix, and no-em/rem rules each appear in both Phase 4b and Key Rules, and the 10-row component inventory table is reference material inlined in the overview.

3 / 5

Actionability

Fully executable guidance throughout: complete script invocations with argument syntax (scaffold.mjs --name/--dir/--brands, generate-base.mjs --input/--output), concrete defaults, a real component tag inventory, and explicit valid/invalid CSS examples with the correct alternative shown.

5 / 5

Workflow Clarity

Phases 1–7 are strictly ordered ("Follow these steps in order. Never skip steps") with an audit checklist and feedback loop in Phase 4b ("fix it immediately before moving to the next phase"), validation against 10 acceptance criteria in Phase 7, user-escalation guidance, and an explicit escape hatch ("basta").

5 / 5

Progressive Disclosure

Clear overview with 18 well-signaled, verified-to-exist references one level deep (including an organized design-foundations/ subdirectory), linked at point of use and in a navigation table; held below 5 because the long Key Rules section and the inner-skill directory tree are inline bulk that partly belongs in reference files.

4 / 5

Total

17

/

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: third-person voice, concrete domain, explicit use-when clause, and a well-chosen trigger list. Slight room to improve via a more comprehensive action enumeration and additional natural synonyms.

DimensionReasoningScore

Specificity

Lists several specific actions — "create, scaffold, or evolve a DS, add components/tokens/themes" — anchored to a concrete domain ("CSS Design Systems based on Chameleon web components"), with minor gaps ("enterprise-quality" is a mild buzzword, actions are broad verb categories rather than a fully enumerated list).

4 / 5

Completeness

Explicitly answers both "what" ("Builds and evolves enterprise-quality CSS Design Systems based on Chameleon web components") and "when" ("Use when the user wants to create, scaffold, or evolve a DS…") with a concrete trigger-phrase list, matching the top anchor.

5 / 5

Trigger Term Quality

Good natural-term coverage ("design system", "DS", "design tokens", "theme system", "build a DS", "scaffold DS", "create design system"), but a few phrases users would naturally say are missing (e.g., "style guide", "brand theme", "UI kit").

4 / 5

Distinctiveness Conflict Risk

Clear niche (Chameleon-based CSS design systems) with distinct triggers, but "design tokens" and "theme system" are broadly applicable terms that create minor overlap risk with generic theming/styling skills.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 6 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 6 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

cinthamo/genexus-skills

Path

frontend/design-system-builder/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.