Name: figma-generate-library
Rating: 76.8 (1 reviews)
Author: figma

figma-generate-library

Build or update a professional-grade design system in Figma from a codebase. Use when the user wants to create variables/tokens, build component libraries, create individual components with proper variant sets and variable bindings, set up theming (light/dark modes), document foundations, or reconcile gaps between code and Figma. Also use when the user asks to create or generate any component in Figma — even a single one — since components require proper variable foundations, variant states, and design token bindings to be production-quality. This skill teaches WHAT to build and in WHAT ORDER — it complements the `figma-use` skill which teaches HOW to call the Plugin API. Both skills should be loaded together.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%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.

A well-architected orchestration skill: actionable, clearly sequenced with validation, and cleanly split across one-level-deep references and helper scripts. The only weakness is mild verbosity from repeated emphases and a few motivational lines that could be trimmed.

Suggestions

Consolidate the "never one-shot / multi-call" message to a single location — it currently repeats across the intro, Section 1, and the critical rules.

Trim rhetorical emphasis lines (e.g. "No best-effort substitutions. No quiet approximations. No handoff with missing source truth...") in favor of the concrete rules that already encode those constraints.

Consider folding the detailed communication-contract update formats in Section 1 into a reference doc, keeping only the contract essentials inline.

Dimension	Reasoning	Score
Conciseness	Mostly lean — uses terse tables, stable task IDs, and assumes Plugin API knowledge without re-explaining basics — but carries some redundant emphasis (the multi-call/never-one-shot message appears in the intro, §1, and the critical rules) and motivational padding ("No best-effort substitutions. No quiet approximations...").	4 / 5
Actionability	Provides executable detail throughout: concrete phase checklists, exact API call patterns with parameters, state-ledger JSON schema, specific scope enums, var() code-syntax rules, a file path for state persistence, and a helper-scripts table mapping each script to its purpose.	5 / 5
Workflow Clarity	Sequenced phases 0–4 with per-phase exit criteria, explicit validation checkpoints (get_metadata after every create, get_screenshot after each component), idempotency checks, and a resume protocol — satisfying the feedback-loop requirement for a destructive/batch workflow.	5 / 5
Progressive Disclosure	SKILL.md is an overview that points to 7 reference docs and 8 helper scripts one level deep, each clearly signaled with phase and load-when metadata in tables; all referenced paths were verified to exist as real bundle files.	5 / 5
	Total	19 / 20 Passed

Description

100%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.

A strong, specific description that clearly states both what the skill does and when to invoke it, with natural trigger phrasing and a distinct niche separated from its companion skill. No vagueness, over-claims, or voice violations detected.

Dimension	Reasoning	Score
Specificity	Enumerates the full activity set — "create variables/tokens, build component libraries, create individual components with proper variant sets and variable bindings, set up theming (light/dark modes), document foundations, or reconcile gaps" — giving comprehensive, concrete coverage rather than a few actions.	5 / 5
Completeness	Explicitly answers both "what" (build/update a professional-grade design system in Figma from a codebase) and "when" ("Use when the user wants to...", "Also use when the user asks to create or generate any component") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Uses natural user phrasing ("create variables/tokens", "build component libraries", "set up theming", "create or generate any component") with synonyms (create/generate, variables/tokens) and a catch-all single-component trigger.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Figma design systems from a codebase) and explicitly differentiates from the sibling figma-use skill; triggers are specific to Figma design-system work, minimizing wrong-skill activation. Voice is third person throughout.	5 / 5
	Total	20 / 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
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: figma/mcp-server-guide
Path: skills/figma-generate-library/SKILL.md
Commit: 72fcf1f

Reviewed: 3 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.