figma-ui-skills

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

Quality

62%

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/figma/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 concise and well-structured with a clear 'Use when' clause that provides explicit trigger guidance. Its main weakness is the lack of specific concrete actions—it describes what the system is but not what it does (e.g., generate components, apply styles, create layouts). The trigger terms are adequate but could benefit from broader coverage of natural user language.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Applies Figma's design system to build UI components, style layouts, and generate consistent interfaces.'

Expand trigger terms to include variations users might naturally say, such as 'Figma-style', 'clean UI', 'modern interface design', or 'design system tokens'.

Dimension	Reasoning	Score
Specificity	Names the domain (UI design system) and mentions some specific details (light mode, Inter font, 4px grid), but doesn't list concrete actions like 'create layouts', 'style components', or 'apply spacing rules'.	2 / 3
Completeness	Clearly answers both what ('Figma's UI design system') and when ('Use when building interfaces inspired by Figma's aesthetic - light mode, Inter font, 4px grid') with an explicit 'Use when' clause and trigger conditions.	3 / 3
Trigger Term Quality	Includes 'Figma', 'UI design system', 'light mode', 'Inter font', and '4px grid' which are relevant but somewhat niche. Missing common user terms like 'design tokens', 'component styling', 'Figma-style', or 'clean UI'.	2 / 3
Distinctiveness Conflict Risk	The specificity to Figma's aesthetic, Inter font, and 4px grid system creates a clear niche that is unlikely to conflict with other design system skills or generic UI skills.	3 / 3
	Total	10 / 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 constraints using MUST/SHOULD/NEVER language and specific values in organized tables. Its main weaknesses are the lack of executable code examples showing implementation (e.g., CSS custom properties, Tailwind config, or component snippets) and some redundant information that inflates token usage without adding value. The content would benefit from being split into a concise overview with links to detailed reference tables.

Suggestions

Add executable code examples showing how to implement the design tokens (e.g., CSS custom properties block, Tailwind config snippet, or a sample React component using the system)

Remove redundant information: drop the RGB column (Claude can convert), remove the 'Count' column from Text Styles, and consolidate the 'Typography Reference' section into the Text Styles table

Split detailed token tables and component specs into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with the most critical constraints and links to details

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., 'Typography Reference' section repeats what's already in the Text Styles table, RGB values alongside HEX are arguably unnecessary for Claude, and the 'Count' column with all 1s adds no value).	2 / 3
Actionability	Provides specific values (colors, sizes, spacing) and clear constraints (MUST/SHOULD/NEVER), which is good for a design system skill. However, it lacks any executable code examples showing how to implement these tokens in CSS/Tailwind/React, making it more of a reference spec than actionable implementation guidance.	2 / 3
Workflow Clarity	For a design system reference skill, there's no multi-step workflow needed, but the 'When to Apply' section is vague and there's no guidance on the order of operations when building a UI (e.g., start with layout, then typography, then colors). The constraints are clear individually but lack a cohesive implementation sequence.	2 / 3
Progressive Disclosure	Content is well-organized with clear section headers and tables, but it's a long monolithic file (~150 lines of detailed specs) that could benefit from splitting detailed token tables and component specs into separate reference files, keeping SKILL.md as a concise overview with links.	2 / 3
	Total	8 / 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.