figma-create-design-system-rules

Generate project-specific design system rules for Figma-to-code workflows. Useful for capturing tokens, naming, and lint rules in one source.

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/figma-create-design-system-rules/SKILL.md

Quality

Content

47%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a thin catalogue/pointer skill that delegates the real workflow to an upstream GitHub repo, so the body offers little actionable or workflow-specific guidance. Its structure is clean and concise, but it lacks executable content for the actual task.

Suggestions

Inline the key workflow steps or a minimal working example (e.g., a sample rules file structure or a command to scaffold tokens) instead of only linking out to the upstream repo.

Provide the concrete install command for placing the upstream bundle in the agent's skills directory rather than instructing the reader to "inspect the upstream README for exact paths".

Remove the duplicated description in the "What it does" section or replace it with content that adds information beyond the frontmatter.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, with only minor redundancy — the "What it does" section repeats the frontmatter description verbatim and could be trimmed.	4 / 5
Actionability	The only executable guidance is `open https://github.com/figma/skills`; it points to an external repo rather than providing concrete steps or code for generating design-system rules.	2 / 5
Workflow Clarity	A rough sequence exists (install upstream bundle, then invoke by name or trigger), but the install step is undefined and there are no validation checkpoints or specifics.	2 / 5
Progressive Disclosure	Short, well-organized sections with a single clearly signaled external reference (the upstream repo); no local bundle files exist to evaluate deeper references.	4 / 5
	Total	12 / 20 Passed

Description

70%Weight 40%Scale 1-5

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 specific and distinct, clearly naming the Figma-to-code design-system domain and the artifacts it captures. Its main weakness is the absence of an explicit "Use when…" trigger clause, leaving the invocation guidance only implied.

Suggestions

Add an explicit "Use when…" clause naming concrete trigger scenarios (e.g., "Use when setting up Figma-to-code lint rules or codifying design tokens for a project").

Include a few natural synonyms or phrasings users might say (e.g., "Figma lint rules", "design tokens to code") to broaden trigger coverage.

Tighten the actions from abstract "generate rules" toward concrete deliverables (e.g., "produces a rules file with token mappings, naming conventions, and lint checks").

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "Generate project-specific design system rules" and "capturing tokens, naming, and lint rules in one source" — though the actions remain somewhat abstract rather than fully comprehensive.	4 / 5
Completeness	It clearly states what the skill does but provides no explicit "Use when…" trigger clause — only "Useful for…" — so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Contains natural domain terms a user would say ("design system rules", "Figma-to-code", "tokens", "lint rules") with good coverage, though a few common synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	The Figma-to-code design-system niche is specific with distinct triggers, giving minimal overlap risk with unrelated skills.	5 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/figma-create-design-system-rules/SKILL.md
Commit: 1a7a23d

Reviewed: about 6 hours 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.