supabase-ui-skills
Supabase's UI design system. Use when building interfaces inspired by Supabase'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/supabase/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 distinctive brand-specific triggers that minimize conflict risk. However, it lacks concrete action verbs describing what the skill actually does (e.g., generating components, applying styles) and could benefit from additional natural trigger terms users might use when requesting Supabase-style interfaces.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates UI components, applies color palettes, and styles layouts following Supabase's design system.'
Include additional natural trigger terms users might say, such as 'dashboard UI', 'Supabase theme', 'dark UI components', or 'Supabase-style design'.
| 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', 'style buttons', or 'build layouts'. | 2 / 3 |
Completeness | Clearly answers both what ('Supabase's UI design system') and when ('Use when building interfaces inspired by Supabase's aesthetic') with explicit trigger guidance including specific aesthetic markers. | 3 / 3 |
Trigger Term Quality | Includes 'Supabase', 'dark mode', 'Inter font', and '4px grid' which are relevant but misses common user terms like 'UI components', 'design tokens', 'theme', 'styling', or 'dashboard'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific brand reference (Supabase) and concrete design attributes (dark mode, Inter font, 4px grid), making it very 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 solid design system reference skill with clear constraints using MUST/SHOULD/NEVER language and well-organized tables of design tokens. Its main weaknesses are the lack of executable code examples showing how to apply these tokens in practice (e.g., CSS variables, Tailwind config, or component snippets) and some redundancy in the reference data. The content would benefit from being split into a concise overview with links to detailed reference files.
Suggestions
Add a quick-start code example showing how to set up the design tokens (e.g., CSS custom properties block or Tailwind config snippet) to improve actionability.
Remove redundant entries: border-radius scale is listed twice, multiple near-identical text-16px rows could be consolidated, and 'detected lightness: 7' / 'currently 16 colors detected' are meta-observations that don't help Claude build UIs.
Consider splitting detailed reference tables (full typography styles, spacing scales, border radius scales) into a separate REFERENCE.md file, 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. However, there's some redundancy (e.g., border-radius scale listed twice, multiple near-identical text-16px entries, 'Detected Layout Patterns' with duplicative entries) and some tokens that don't add value (like 'Count' column showing all 1s, 'detected lightness: 7'). | 2 / 3 |
Actionability | The skill provides concrete design tokens, specific values, and clear constraints (MUST/SHOULD/NEVER), which is actionable for a design system skill. However, it lacks executable code examples showing how to apply these tokens in practice (e.g., a Tailwind config snippet, CSS custom properties setup, or a component example), which would make it more immediately usable. | 2 / 3 |
Workflow Clarity | This is a reference/constraint skill rather than a multi-step workflow, so the single-task clarity standard applies. The content is well-organized with clear sections, unambiguous rules using MUST/SHOULD/NEVER language, and specific values for each design decision. No destructive or batch operations are involved. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and tables, but it's a fairly long monolithic document (~150 lines of design tokens and rules). Some sections like the full typography reference table and detailed spacing/border scales could be split into separate reference files, with the SKILL.md providing a concise overview and linking out. | 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.