loops-ui-skills
Loops's UI design system. Use when building interfaces inspired by Loops's aesthetic - light mode, Inter font, 4px grid.
67
58%
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/loops/SKILL.mdQuality
Discovery
67%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 concise and includes an explicit 'Use when' clause, which is good for completeness. However, it lacks concrete actions (what the skill actually does beyond defining a design system) and could benefit from more specific capability descriptions. The distinctiveness is moderate—while 'Loops' is a specific brand, the broader terms could overlap with generic UI design skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates components, styles layouts, and applies design tokens following Loops's UI design system.'
Expand trigger terms to include variations like 'Loops-style', 'Loops aesthetic', 'email platform UI', or 'Loops brand' to improve matching and reduce ambiguity with programming loop concepts.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (UI design system) and mentions some specific elements like 'light mode, Inter font, 4px grid', but doesn't list concrete actions (e.g., 'create buttons, style forms, build layouts'). It describes attributes rather than actions. | 2 / 3 |
Completeness | Clearly answers both 'what' (Loops's UI design system with light mode, Inter font, 4px grid) and 'when' (Use when building interfaces inspired by Loops's aesthetic), with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'Loops', 'UI design system', 'light mode', 'Inter font', '4px grid', but misses common variations users might say such as 'design tokens', 'component styling', 'Loops-style', or 'email marketing UI'. The brand name 'Loops' is a good trigger but could be confused with loop constructs in code. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Loops' as a specific brand provides some distinctiveness, but 'UI design system' is quite broad and could overlap with other design system skills. The term 'Loops' could also be confused with programming loop concepts, creating potential false triggers. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
50%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 constraint language (MUST/SHOULD/NEVER) and specific values. Its main weaknesses are the lack of executable code examples showing implementation, some redundant/raw data that could be trimmed or moved to reference files, and the absence of a workflow for applying these guidelines when building a component or page.
Suggestions
Add executable code examples (CSS custom properties, Tailwind config, or component snippets) showing how to implement the design tokens in practice
Remove redundant sections (e.g., Border Radius Reference duplicates the Borders section scale) and move detailed reference tables (all 10 text styles, full font size list) to a separate REFERENCE.md
Add a brief workflow section showing the sequence for building a component: e.g., 1) Set up tokens, 2) Apply typography scale, 3) Check contrast ratios, 4) Verify grid alignment
Clean up raw extracted data (e.g., 'currently 17 colors detected', 'used 86x', element widths like '13px, 27px, 50px, 12px, 7px') - either contextualize these or remove them
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with well-structured tables and clear MUST/SHOULD/NEVER constraints, but includes some redundant information (e.g., 'Border Radius Reference' section repeats the scale already listed in the Borders section, and the 'Typography Reference' section partially duplicates the Text Styles table). The detected layout patterns and element widths feel like raw extracted data rather than curated guidance. | 2 / 3 |
Actionability | Provides specific values (hex codes, pixel sizes, font weights) and clear constraint language (MUST/SHOULD/NEVER), which is actionable for design implementation. However, it lacks executable code examples - no CSS snippets, no Tailwind classes, no component code showing how to actually implement these tokens in practice. | 2 / 3 |
Workflow Clarity | The 'When to Apply' section provides clear triggers, and the content is well-organized by category. However, there's no workflow for how to actually build a component or page using these guidelines - no sequenced steps, no validation checkpoints for checking contrast ratios or grid alignment. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but it's a monolithic file with a lot of detail inline. The extensive text styles table (10 rows), font sizes list, and border radius scales could be split into reference files, with the main skill focusing on the most important constraints and patterns. | 2 / 3 |
Total | 8 / 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.