Figma use_figma Plugin API Rules
warpdotdev/warp
Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.
Look up Spectrum design tokens, component schemas, and design-system decisions when building with or extending Adobe Spectrum.
$ npx skills add adobe/spectrum-design-data --skill design-data -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install adobe/spectrum-design-data design-data --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/adobe/spectrum-design-data.git skills-src && mkdir -p .claude/skills && cp -r skills-src/tools/design-data-skill/skills/design-data .claude/skills/design-data && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "design-data" agent skill from https://github.com/adobe/spectrum-design-data/tree/main/tools/design-data-skill/skills/design-data into .claude/skills/design-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-data", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/adobe/spectrum-design-data/tree/main/tools/design-data-skill/skills/design-dataType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add adobe/spectrum-design-data --skill design-data -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install adobe/spectrum-design-data design-data --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/adobe/spectrum-design-data.git skills-src && mkdir -p .agents/skills && cp -r skills-src/tools/design-data-skill/skills/design-data .agents/skills/design-data && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "design-data" agent skill from https://github.com/adobe/spectrum-design-data/tree/main/tools/design-data-skill/skills/design-data into .agents/skills/design-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-data", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add adobe/spectrum-design-data --skill design-data -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install adobe/spectrum-design-data design-data --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/adobe/spectrum-design-data.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/tools/design-data-skill/skills/design-data .cursor/skills/design-data && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "design-data" agent skill from https://github.com/adobe/spectrum-design-data/tree/main/tools/design-data-skill/skills/design-data into .cursor/skills/design-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-data", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/adobe/spectrum-design-data.git --path tools/design-data-skill/skills/design-data--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add adobe/spectrum-design-data --skill design-data -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install adobe/spectrum-design-data design-data --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/adobe/spectrum-design-data.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/tools/design-data-skill/skills/design-data .gemini/skills/design-data && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "design-data" agent skill from https://github.com/adobe/spectrum-design-data/tree/main/tools/design-data-skill/skills/design-data into .gemini/skills/design-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-data", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install adobe/spectrum-design-data design-dataInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add adobe/spectrum-design-data --skill design-data -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/adobe/spectrum-design-data.git skills-src && mkdir -p .github/skills && cp -r skills-src/tools/design-data-skill/skills/design-data .github/skills/design-data && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "design-data" agent skill from https://github.com/adobe/spectrum-design-data/tree/main/tools/design-data-skill/skills/design-data into .github/skills/design-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-data", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add adobe/spectrum-design-data --skill design-data -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install adobe/spectrum-design-data design-data --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/adobe/spectrum-design-data.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/tools/design-data-skill/skills/design-data .opencode/skills/design-data && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "design-data" agent skill from https://github.com/adobe/spectrum-design-data/tree/main/tools/design-data-skill/skills/design-data into .opencode/skills/design-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-data", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
design-dataLook up Spectrum design tokens, component schemas, and design-system decisions when building with or extending Adobe Spectrum.
Design Data is an agent skill from adobe/spectrum-design-data. Look up Spectrum design tokens, component schemas, and design-system decisions when building with or extending Adobe Spectrum. Use when the user asks about token values, component options, naming conventions, or wants to validate/explore design-token data. Also triggers when a .design-data.toml config is involved or the user mentions the design-data CLI.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design, covering Design tokens and Design systems. It works with Model Context Protocol. The repository describes itself as: Design data, including design tokens, component schemas, and tooling for Spectrum, Adobe's design system. The licence is Apache-2.0.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit dc75d47. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
mcp__design-data__design-data-primermcp__design-data__design-data-querymcp__design-data__design-data-suggestmcp__design-data__design-data-componentmcp__design-data__design-data-resolveFrom allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are json and toml).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Design Data loads about 1.2k tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 415 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from adobe/spectrum-design-data at commit dc75d47, republished under its Apache-2.0 licence (© adobe). 415 words, ~1,199 tokens.
.claude/skills/design-data/SKILL.md (or your agent's skills folder).Access Spectrum design tokens, component schemas, and design-system structure
via the @adobe/design-data-mcp MCP server (in-process wasm — no CLI binary required).
Add @adobe/design-data-mcp to your project's .cursor/mcp.json (or equivalent
MCP config) to activate the tools:
{
"mcpServers": {
"design-data": {
"command": "npx",
"args": ["-y", "@adobe/design-data-mcp"]
}
}
}The server uses an embedded Spectrum snapshot — no environment variables or dataset path configuration required for read operations.
design-data-primerGet a structural overview of the embedded Spectrum dataset: token count, available mode-sets (color-scheme, scale, contrast), component list, taxonomy fields, and data provenance. Call this at the start of a design-token session.
No required inputs.
design-data-queryFilter Spectrum tokens by a query expression. Returns an array of matching token objects.
Required input: filter (string)
Expression syntax examples:
"component=button" — all button tokens"component=button,state=hover" — button hover tokens"property=color-*" — all color property tokens"colorScheme=dark" — dark-scheme tokensReturns an empty array when no tokens match.
design-data-suggestSuggest Spectrum tokens matching a natural-language intent using keyword-overlap scoring. Returns matches ranked by confidence.
Required input: intent (string) — e.g. "primary CTA button background color"
Optional input: limit (number, default 5)
design-data-componentGet the full component declaration for a Spectrum component by ID. Returns the component's displayName, description, and all available options (variants, sizes, states, boolean props, etc.).
Required input: id (string) — kebab-case component ID, e.g. button, action-button
Call design-data-primer first to see available component IDs.
design-data-resolveResolve the concrete value of a Spectrum token property for a given mode-set context. Returns the winning token with its resolved value.
Required input: property (string) — token property name, e.g. background-color-default
Optional inputs: colorScheme ("light" or "dark"), scale ("desktop" or "mobile"),
contrast ("regular" or "high")
design-data-primer to understand what data is available.design-data-query when you know the component/property/state.design-data-suggest when the user describes an intent in natural language.design-data-component to check all available options for a specific component.design-data-resolve to get the concrete value for a token in a given context.Install this skill as a Remote Rule (GitHub) — same pattern as the s2-docs skill:
Cursor Settings → Rules → Add Rule → Remote Rule (GitHub) → paste:
https://github.com/adobe/spectrum-design-data/tree/main/tools/design-data-skill/skills/design-dataFor always-available tool access (higher context cost), add the MCP server to
.cursor/mcp.json as shown in the Bootstrap section above.
For custom datasets with validate/diff/write, use the design-data-agent skill or
@adobe/design-data-agent-mcp instead — see
tools/design-data-agent-mcp/skills/design-data/SKILL.md.
To point at a specific Spectrum version or a custom design-data fork, add
a .design-data.toml to your project root:
[source]
type = "github"
repo = "adobe/spectrum-design-data"
tag = "@adobe/spectrum-tokens@14.11.0"Without a config file, the embedded Spectrum snapshot is used automatically.
© adobe, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in tools/design-data-skill/skills/design-data of adobe/spectrum-design-data.
Open the folder on GitHubat commit dc75d47
Design Data next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Design Data this skilladobe/spectrum-design-data | 155 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Figma use_figma Plugin API Ruleswarpdotdev/warp | 65k | 4 repos | ~4.4k | Automated safety check: Pass | AGPL-3.0 | |
| Figma Screen Generatorwarpdotdev/warp | 65k | 2 repos | ~5k | Automated safety check: Pass | AGPL-3.0 | |
| Extract Design Systemarvindrk/extract-design-system | 236 | 1 repos | ~514 | Automated safety check: Pass | MIT | |
| Website Design Taste Extractorsenlindesign/taste-skill | 381 | — | ~5.3k | Automated safety check: Pass | None | |
| Montage Reactwanteddev/montage-web | 117 | — | ~3.4k | Automated safety check: Pass | MIT |
warpdotdev/warp
Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.
warpdotdev/warp
Builds or updates full Figma screens from code or a description by reusing the file's published design system components, variables and styles.
arvindrk/extract-design-system
Extract design primitives from a public website and generate starter token files for your project.
senlindesign/taste-skill
Reverse-engineers a website's design from its URL into a Markdown and JSON pair holding concrete tokens and the trade-offs behind the look.
wanteddev/montage-web
Guide for building UI with Montage (Wanted Design System) in React/Next.js projects.
asgeirtj/system_prompts_leaks
Inspects Figma designs through the figma CLI and Figma's MCP server to read variants, spacing, tokens and layouts and to extract assets for implementation.
adobe/spectrum-design-data
Look up Spectrum 2 (S2) component documentation, design guidelines, and usage patterns when building with React Spectrum or Spectrum Web Components.
adobe/spectrum-design-data
Validate, query, resolve, diff, and author spec-conformant design tokens and components using the design-data MCP tools against a local dataset.
adobe/spectrum-design-data
Enhances auto-generated spectrum-design-data PRs from spectrum-tokens-studio-data sync (branch tokens-sync/patch-spectrum2-from-main, author mrcjhicks).
adobe/spectrum-design-data
Reviews docs-site prose (articles, spec pages, READMEs) against Spectrum's voice principles (Clear, Genuine, Concise, Upfront), adapted for public/reference docs rather than in-product UI strings.
Works with
Categories
Look up Spectrum design tokens, component schemas, and design-system decisions when building with or extending Adobe Spectrum. Design Data is an agent skill from adobe/spectrum-design-data. Look up Spectrum design tokens, component schemas, and design-system decisions when building with or extending Adobe Spectrum.
Design Data fits situations like: the user asks about token values; component options; naming conventions; wants to validate/explore design-token data.
Run `npx skills add adobe/spectrum-design-data --skill design-data -a claude-code`. Or copy the skill folder (tools/design-data-skill/skills/design-data in adobe/spectrum-design-data) into .claude/skills/design-data in your project. Claude Code loads it when a task matches its description.
Run `npx skills add adobe/spectrum-design-data --skill design-data -a codex`. Or copy the skill folder (tools/design-data-skill/skills/design-data in adobe/spectrum-design-data) into .agents/skills/design-data in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add adobe/spectrum-design-data --skill design-data -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/design-data, .gemini/skills/design-data, .github/skills/design-data and .opencode/skills/design-data in your project.
SKILL.md names no scripts, command-line tools or credentials: Design Data is instructions for the agent only. Its frontmatter pre-approves these tools: mcp__design-data__design-data-primer, mcp__design-data__design-data-query, mcp__design-data__design-data-suggest, mcp__design-data__design-data-component, mcp__design-data__design-data-resolve.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Design Data is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Design Data: Figma use_figma Plugin API Rules (warpdotdev/warp, 65k stars), Figma Screen Generator (warpdotdev/warp, 65k stars), Extract Design System (arvindrk/extract-design-system, 236 stars) and Website Design Taste Extractor (senlindesign/taste-skill, 381 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
adobe (a GitHub organization) maintains it in adobe/spectrum-design-data, which has 155 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 2, 2026.
Source: adobe/spectrum-design-data on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.