ui-design-system
UI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use for creating design systems, maintaining visual consistency, and facilitating design-dev collaboration.
90
77%
Does it follow best practices?
Impact
98%
1.12xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./product-team/ui-design-system/SKILL.mdQuality
Discovery
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 does a good job listing specific capabilities and includes an explicit 'Use for...' clause covering both what and when. However, trigger term coverage could be broader with more natural user-facing keywords, and the inclusion of 'Senior UI Designer' as a persona is unnecessary and slightly confusing. Some terms like 'visual consistency' and 'design-dev collaboration' are broad enough to risk overlap with adjacent skills.
Suggestions
Add more natural trigger terms users would say, such as 'style guide', 'color palette', 'spacing scale', 'breakpoints', 'typography tokens', 'UI kit', or 'Figma handoff'.
Remove the persona reference 'for Senior UI Designer' as it doesn't aid skill selection and replace with more specific trigger scenarios like 'Use when the user asks about design tokens, component specs, responsive breakpoints, or preparing designs for developer implementation'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'design token generation', 'component documentation', 'responsive design calculations', and 'developer handoff tools'. These are distinct, identifiable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('design token generation, component documentation, responsive design calculations, developer handoff tools') and when ('Use for creating design systems, maintaining visual consistency, and facilitating design-dev collaboration'). The 'Use for...' clause serves as an explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'design tokens', 'component documentation', 'responsive design', 'developer handoff', and 'design systems', but misses common user variations like 'style guide', 'UI kit', 'spacing scale', 'color palette', 'breakpoints', or 'Figma'. The terms lean slightly technical rather than how users naturally phrase requests. | 2 / 3 |
Distinctiveness Conflict Risk | While 'design token generation' and 'developer handoff tools' are fairly distinctive, terms like 'visual consistency' and 'design-dev collaboration' are broad enough to potentially overlap with general frontend development or CSS skills. The 'Senior UI Designer' persona mention is unusual and doesn't help with disambiguation. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
N/AReviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
Something went wrong
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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- alirezarezvani/claude-skills
- Commit
967fe01
- 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.