SKILLEMALL.ai
GitHub ↗ RU Sign in

CC 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.

The skillemall take

Promises to build a design system in Figma from scratch: variables, components with variants, token bindings, light/dark modes. Contains 16 files and 8 scripts for variable binding, component creation, and documentation. Quality score 73, process score 64. Broken references exist but don't block execution.

Sandbox test: scripts stayed within their folder, ran quietly. No critical issues found. This teaches the sequence—tokens first, then components, then variants—not the API itself; use alongside figma-use for that. Install if you're willing to work through the guide and don't expect turnkey code for every scenario.

anomalyco/opencode Claude Code author: anomalyco MIT 16 files · 8 scripts body ≈ 5 907 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Build or update a professional-grade design system in Figma from a codebase.

As a process C 64/100 · Has gaps — References files that are not bundled: ../figma-use/references/gotchas.md

GeneratorFigmaDesigntype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
73
Run on models
none yet
Process rating
C
64/100
Has gaps
References files that are not bundled: ../figma-use/references/gotchas.md
Tools and files w 18
0
Progress reporting w 2
0
Result and completion w 14
40
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: opencode

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 16. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 5907 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: ../figma-use/references/gotchas.md

Process rating: all ten parameters 64/100

Will not run. References files that are not bundled: ../figma-use/references/gotchas.md
  • 0Tools and files. 1 referenced file(s) missing: ../figma-use/references/gotchas.md
  • 0Progress reporting. Says nothing while it works
  • 40Result and completion. Does not say what the result is
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 5907 tokens
  • 85Steps. 69 steps, 1 vague phrases
  • 100When it triggers. States when to use and when not to
  • 100Failures and branches. 2 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 11 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -215 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +3Description length 719: enough signal without eating the budget
  • +4Structure: 18 headings
  • +3Step-by-step instructions: 69 items
  • +4Has examples (6 code blocks)
  • +4Reference files are cited in the instructions (7 of 7)
  • +3All 8 scripts are documented

Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.

In the sandbox The scripts kept to themselves

The skill's scripts were run in a throwaway machine: no network, fake keys in the home directory, a tracer watching. We wrote down what they did. Reaching for the network or for secrets caps the technical grade at C; a quiet run adds no points.

Запущено 8 скриптов; каждому дали двадцать секунд, поддельный домашний каталог с ключами и сеть, в которой ничего нет.

scripts/bindVariablesToComponent.jsничего за пределами своей папки
scripts/cleanupOrphans.jsничего за пределами своей папки
scripts/createComponentWithVariants.jsничего за пределами своей папки
scripts/createDocumentationPage.jsничего за пределами своей папки
scripts/createSemanticTokens.jsничего за пределами своей папки
scripts/createVariableCollection.jsничего за пределами своей папки
scripts/inspectFileStructure.jsничего за пределами своей папки
scripts/validateCreation.jsничего за пределами своей папки

15 Oct 2026