bear-ui-skills
Bear's UI design system. Use when building interfaces inspired by Bear's aesthetic - light 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/bear/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 concise and well-structured with a clear 'Use when' clause and distinctive identity tied to Bear's design system. Its main weakness is the lack of specific concrete actions—it tells Claude the aesthetic parameters but not what it can actually do (e.g., generate components, apply spacing, create layouts). Trigger term coverage could also be broader.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates UI components, applies consistent spacing and typography, creates styled layouts following Bear's design system.'
Expand trigger terms to include variations users might say, such as 'Bear app style', 'design tokens', 'component styling', 'theme', or 'minimal UI'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (UI design system) and mentions some specific elements (light mode, Inter font, 4px grid), but doesn't list concrete actions like 'create components', 'apply spacing tokens', or 'generate layouts'. | 2 / 3 |
Completeness | Clearly answers both what ('Bear's UI design system') and when ('Use when building interfaces inspired by Bear's aesthetic - light mode, Inter font, 4px grid') with an explicit 'Use when' clause and specific trigger conditions. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'UI design system', 'Bear', 'light mode', 'Inter font', '4px grid', but misses common variations users might say such as 'design tokens', 'component library', 'styling', 'theme', or 'Bear app'. | 2 / 3 |
Distinctiveness Conflict Risk | The reference to 'Bear's aesthetic' combined with specific design parameters (Inter font, 4px grid, light mode) creates a clear niche that is unlikely to conflict with generic UI or 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 with clear constraints using MUST/SHOULD/NEVER language and well-organized token tables. Its main weaknesses are the lack of executable code examples (CSS custom properties, Tailwind config, or component snippets) and some redundancy in the reference data. The content would benefit from concrete implementation examples and better progressive disclosure for the detailed specifications.
Suggestions
Add executable code examples: a CSS custom properties block defining the design tokens, or a Tailwind config snippet, so Claude can directly apply the system rather than translating tables into code.
Remove redundant information like the border-radius scale appearing twice and the 'Count' column in text styles, and consolidate the detected layout patterns section which adds minimal value.
Split detailed reference tables (all text styles, full font size list) into a separate REFERENCE.md file, keeping only the most commonly used tokens in the main skill.
| 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, 'Count' column in text styles adds little value, detected layout patterns section is thin). The raw data dumps like all font sizes and element widths feel like they could be tightened. | 2 / 3 |
Actionability | The skill provides specific values (hex codes, pixel sizes, font weights) which are concrete and directly usable. However, it lacks executable code examples — no CSS snippets, no Tailwind classes, no component templates. For a UI design system skill, showing a concrete component implementation or CSS custom properties block would significantly improve actionability. | 2 / 3 |
Workflow Clarity | This is a reference/constraint skill rather than a multi-step workflow. The single-purpose nature (apply these design tokens when building Bear-style UIs) is unambiguous. The MUST/SHOULD/NEVER hierarchy provides clear decision-making guidance, and the 'When to Apply' section clearly scopes usage. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and tables, but it's a fairly long monolithic document (~150 lines) that could benefit from splitting detailed token tables and component specs into separate reference files. No external references are provided for deeper dives into specific areas like components or animation patterns. | 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.