spotify-ui-skills
Spotify's UI design system. Use when building interfaces inspired by Spotify's aesthetic - dark mode, Inter font, 4px grid.
75
68%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/spotify/SKILL.mdQuality
Discovery
75%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 well-structured with a clear 'Use when' clause and distinct branding that makes it easy to identify. Its main weakness is the lack of specific concrete actions—it describes what the system is but not what it does (e.g., generating components, applying styles). The trigger terms could also be expanded to cover more natural user phrasings.
Suggestions
Add specific concrete actions like 'Creates components, applies color tokens, builds card layouts, and styles navigation elements following Spotify's design system'.
Expand trigger terms to include variations users might say, such as 'Spotify-style', 'music app UI', 'green accent theme', or 'streaming interface'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (UI design system) and mentions some specific elements (dark mode, Inter font, 4px grid), but doesn't list concrete actions like 'create components', 'apply color tokens', or 'build layouts'. | 2 / 3 |
Completeness | Clearly answers both what ('Spotify's UI design system') and when ('Use when building interfaces inspired by Spotify's aesthetic - dark mode, Inter font, 4px grid') with an explicit 'Use when' clause and trigger conditions. | 3 / 3 |
Trigger Term Quality | Includes 'Spotify', 'dark mode', 'Inter font', and '4px grid' which are relevant, but misses common user terms like 'music app UI', 'green accent', 'card layout', 'Spotify-style', or 'streaming app design'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Spotify's specific design system with distinct identifiers (Spotify, Inter font, 4px grid, dark mode), making it unlikely to conflict with other design system skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a reasonably well-structured design system reference with clear constraints using MUST/SHOULD/NEVER language and specific values. Its main weaknesses are the lack of executable code examples (CSS/Tailwind snippets, component templates) that would make it immediately actionable, and some raw data that feels auto-generated rather than curated (duplicate text style entries, verbose element width lists). The content would benefit from trimming redundant data and adding concrete implementation snippets.
Suggestions
Add executable code examples—e.g., a Tailwind config snippet for the color tokens, a CSS custom properties block, or a sample component showing the design system in use.
Consolidate the typography section: merge the Text Styles table and Typography Reference into a single concise reference, removing near-duplicate entries (e.g., multiple text-15px rows with slightly different colors).
Move detailed reference tables (full text styles, detected layout patterns) to a separate REFERENCE.md file and link to it, keeping SKILL.md as a concise overview with the most critical tokens and rules.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with well-structured tables and clear MUST/SHOULD/NEVER constraints, but includes some redundancy (e.g., the typography section has both a 'Text Styles' table and a separate 'Typography Reference' section listing the same font sizes). The detected layout patterns and element widths feel like raw data dumps rather than curated guidance. Some tables have excessive rows with near-duplicate entries (multiple text-15px variants). | 2 / 3 |
Actionability | The skill provides specific values (hex codes, pixel sizes, timing constraints) which is good, but lacks executable code examples. For a UI design system skill, concrete CSS/Tailwind snippets or component code would significantly improve actionability. The guidance is specific but descriptive rather than directly implementable—e.g., 'lighten background by 10%' without showing how. | 2 / 3 |
Workflow Clarity | This is a reference/constraint skill rather than a multi-step workflow, so the single-purpose nature applies. The content is clearly organized by concern (colors, typography, spacing, etc.) with unambiguous rules using MUST/SHOULD/NEVER modifiers. The 'When to Apply' section clearly scopes when to use the skill. | 3 / 3 |
Progressive Disclosure | The content is well-sectioned with clear headers and tables, but it's a fairly long monolithic document. The typography section in particular could benefit from splitting detailed text style tables into a separate reference file. There are no cross-references to external files for deeper detail, and some sections (like the full font size list and text styles table) could be offloaded. | 2 / 3 |
Total | 9 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- ihlamury/design-skills
- Commit
126714e
- 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.