mem-ui-skills

Mem's UI design system. Use when building interfaces inspired by Mem's aesthetic - light mode, Inter font, 4px grid.

Quality

68%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/mem/SKILL.md

Quality

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 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 trigger terms users might naturally use.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Generates UI components, applies consistent spacing, and styles elements following Mem's design system.'

Include additional natural trigger terms users might say, such as 'design tokens', 'component styling', 'Mem theme', or 'Mem-inspired layout'.

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', 'style layouts', or 'apply typography rules'.	2 / 3
Completeness	Clearly answers both what ('Mem's UI design system') and when ('Use when building interfaces inspired by Mem's aesthetic - light mode, Inter font, 4px grid'), with an explicit 'Use when' clause and trigger conditions.	3 / 3
Trigger Term Quality	Includes some relevant keywords like 'Mem', 'UI design system', 'light mode', 'Inter font', '4px grid', but misses common variations users might say such as 'design tokens', 'component library', 'styling', 'theme', or 'Mem-style'.	2 / 3
Distinctiveness Conflict Risk	The description is clearly scoped to Mem's specific design system with distinct identifiers (Mem brand, Inter font, 4px grid, light mode), making it unlikely to conflict with other generic UI or design 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-structured tables for design tokens. Its main weaknesses are the lack of any executable code examples (CSS, Tailwind config, or component snippets) and some redundant granularity in the typography section that could be condensed or moved to a reference file.

Suggestions

Add at least one concrete code example - e.g., CSS custom properties setup for the semantic tokens, or a Tailwind config snippet mapping the design tokens

Consolidate the 8 body-secondary text style variants into a single entry with a note about the size range (18-20px), or move the full table to a separate TYPOGRAPHY_REFERENCE.md

Consider splitting detailed reference tables (full text styles, spacing scale, border-radius scale) into a separate reference file, keeping SKILL.md as a concise overview with the most important constraints and quick-reference values

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with well-structured tables and clear MUST/SHOULD/NEVER constraints. However, the Text Styles table contains excessive granularity (8 variants of body-secondary with slightly different pixel sizes and hex colors) that adds noise without clear actionable value. The Typography Reference section partially duplicates information already in the table.	2 / 3
Actionability	The skill provides concrete design tokens, specific values, and clear constraints (MUST/SHOULD/NEVER). However, it lacks any executable code examples - no CSS snippets, no Tailwind config, no component code. For a UI design system skill, at least one concrete implementation example (e.g., a button component or CSS custom properties setup) would make it significantly more actionable.	2 / 3
Workflow Clarity	This is a reference/constraint skill rather than a multi-step workflow skill. The single-purpose nature (apply these design tokens and rules when building UI) is unambiguous. The MUST/SHOULD/NEVER hierarchy provides clear priority ordering, 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). The detailed text styles table with 10 rows of minor variations and the full border-radius/spacing scales could be split into a reference file, keeping SKILL.md as a concise overview with links to detailed specs.	2 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

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: 8 days ago

Table of Contents

Discovery Implementation Validation

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.