SKILLEMALL.ai
GitHub ↗ RU Sign in

AB 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, set up theming (light/dark modes), document foundations, or reconcile gaps between code and Figma. 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.

warpdotdev/warp Claude Code author: warpdotdev AGPL-3.0 17 files · 9 scripts body ≈ 4 295 tokens Open the sourcegithub.com↗ analyzed 6 d ago

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

As a process B 72/100 · Nearly there — weak spots: result and completion, progress reporting

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
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
89
Run on models
none yet
Process rating
B
72/100
Nearly there
Result and completion w 14
0
Progress reporting w 2
0
Tools and files w 18
60
the three weakest of ten parameters · all ten

How to improve

    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: 17. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 72/100

    • 0Result and completion. Does not say what the result is
    • 0Progress reporting. Says nothing while it works
    • 60Tools and files. Uses tools (node) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 70Execution cost. Instruction body is 4295 tokens
    • 100Steps. 54 steps
    • 100When it triggers. States when to use and when not to
    • 100Failures and branches. 1 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
    • -223 emoji in the instructions: noise for the model
    • +1No license
    • +2Single-language instructions
    • +3Description length 425: enough signal without eating the budget
    • +4Structure: 12 headings
    • +3Step-by-step instructions: 54 items
    • +4Has examples (7 code blocks)
    • +4Reference files are cited in the instructions (7 of 7)
    • +3All 9 scripts are documented

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