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.
Implement supplied Figma designs, screenshots or design specifications as working interfaces.
Install Design To Code
$ npx skills add WrongStack/WrongStack --skill design-to-code -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install WrongStack/WrongStack design-to-code --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/WrongStack/WrongStack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/core/skills/design-to-code .claude/skills/design-to-code && 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-to-code" agent skill from https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/design-to-code into .claude/skills/design-to-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-to-code", 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/WrongStack/WrongStack/tree/main/packages/core/skills/design-to-codeType 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 WrongStack/WrongStack --skill design-to-code -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install WrongStack/WrongStack design-to-code --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WrongStack/WrongStack.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/core/skills/design-to-code .agents/skills/design-to-code && 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-to-code" agent skill from https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/design-to-code into .agents/skills/design-to-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-to-code", 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 WrongStack/WrongStack --skill design-to-code -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install WrongStack/WrongStack design-to-code --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WrongStack/WrongStack.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/core/skills/design-to-code .cursor/skills/design-to-code && 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-to-code" agent skill from https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/design-to-code into .cursor/skills/design-to-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-to-code", 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/WrongStack/WrongStack.git --path packages/core/skills/design-to-code--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 WrongStack/WrongStack --skill design-to-code -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install WrongStack/WrongStack design-to-code --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WrongStack/WrongStack.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/core/skills/design-to-code .gemini/skills/design-to-code && 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-to-code" agent skill from https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/design-to-code into .gemini/skills/design-to-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-to-code", 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 WrongStack/WrongStack design-to-codeInstalls 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 WrongStack/WrongStack --skill design-to-code -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/WrongStack/WrongStack.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/core/skills/design-to-code .github/skills/design-to-code && 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-to-code" agent skill from https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/design-to-code into .github/skills/design-to-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-to-code", 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 WrongStack/WrongStack --skill design-to-code -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install WrongStack/WrongStack design-to-code --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WrongStack/WrongStack.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/core/skills/design-to-code .opencode/skills/design-to-code && 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-to-code" agent skill from https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/design-to-code into .opencode/skills/design-to-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-to-code", 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.
Facts
- Skill name
design-to-code- GitHub stars
- 371
- Token cost
- ~800 tokens
- SKILL.md length
- 300 words
- Files
- 1
- Skills in repo
- 100
- Repo updated
- First seen
- Licence
- MIT
At a glance
Implement supplied Figma designs, screenshots or design specifications as working interfaces.
- Works in 6 steps: Identify reference frame, viewport,… → Extract reusable roles for typography,… → Map visual elements to semantic… → …
- Matching a reference
- SKILL.md covers Selection card, Overview, Rules and Workflow, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Design To Code is an agent skill from WrongStack/WrongStack. Implement supplied Figma designs, screenshots or design specifications as working interfaces. Use when matching a reference or handling design handoff; inspect the actual artifact and preserve its layout, content and interaction intent.
Its SKILL.md is about 800 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 to code. It works with Figma. The repository describes itself as: An AI coding agent that reads your code, edits files, runs commands, and reasons through bugs — across a terminal REPL, a full-screen TUI, and a browser UI, while you keep your… The licence is MIT.
When your agent uses it
- Matching a reference
- Handling design handoff
- Inspect the actual artifact and preserve its layout
- Content and interaction intent
Example prompts
- “/design-to-code”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Identify reference frame, viewport, content and states; distinguish a literal match from an authorized adaptation.
- Extract reusable roles for typography, spacing, color and assets before creating arbitrary per-element values.
- Map visual elements to semantic components. A screenshot does not reveal keyboard behavior or data contracts.
- Verify licensed fonts/assets and available variants; record substitutions with their effect on wrapping and geometry.
- Prefer existing primitives and tokens. Do not rebuild a design system merely because the handoff uses different names.
- Preserve real interactions; decorative controls cannot substitute for functioning navigation or forms.
What it can do on your machine
Read from SKILL.md and the folder at commit a744bdc. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
developers.figma.comdeveloper.mozilla.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Design To Code loads about 800 tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 300 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from WrongStack/WrongStack at commit a744bdc, republished under its MIT licence (© WrongStack). 300 words, ~800 tokens.
Download SKILL.mdSave it as
.claude/skills/design-to-code/SKILL.md (or your agent's skills folder).- name
- design-to-code
- description
- Implement supplied Figma designs, screenshots or design specifications as working interfaces. Use when matching a reference or handling design handoff; inspect the actual artifact and preserve its layout, content and interaction intent.
- trigger
- Implement supplied Figma designs, screenshots or design specifications as working interfaces. Use when matching a reference or handling design handoff…
- version
- 1.0.1
- required-capabilities
- filesystem.read
- optional-capabilities
- filesystem.write, execution.shell, verification.run, web.research
- metadata.routing-group
- design
- metadata.domain
- design
Design To Code
Selection card
- Task: Implement a supplied design or Figma reference. / TR: Verilen tasarım veya Figma referansını uygula.
- Start: Identify the target surface, reference, user task and existing tokens.
- Finish: apply the acceptance checks below; report observed results and unresolved constraints.
Overview
Implement supplied Figma designs, screenshots or design specifications as working interfaces.
Use the existing framework and latest stable target when a new project or upgrade is requested. A Figma link needs an accessible design source; never pretend to have inspected an unavailable file.
Rules
- Identify reference frame, viewport, content and states; distinguish a literal match from an authorized adaptation.
- Extract reusable roles for typography, spacing, color and assets before creating arbitrary per-element values.
- Map visual elements to semantic components. A screenshot does not reveal keyboard behavior or data contracts.
- Verify licensed fonts/assets and available variants; record substitutions with their effect on wrapping and geometry.
- Prefer existing primitives and tokens. Do not rebuild a design system merely because the handoff uses different names.
- Preserve real interactions; decorative controls cannot substitute for functioning navigation or forms.
Workflow
- Inspect the reference and existing implementation; record key geometry and missing states.
- Implement structure, then typography/spacing, then color/assets and interactions.
- Render at the reference viewport and compare alignment, line breaks, density and crop.
- Check narrow/short viewports and long content rather than inferring responsiveness from one frame.
- Correct observed differences and document justified adaptations.
Before returning
Reference access and viewport recorded; assets/fonts verified; rendered comparison and actual interaction checks separated from source inspection.
Sources
Versioned facts checked 2026-10-09; refresh authoritative sources before new installs/upgrades. Figma developer resources, Web layout.
Skills in scope
- design-system — tokens and shared component state.
- design-craft — product-specific composition.
- design-critique — rendered evidence and ranked findings.
- interaction-design — task/state transition design.
© WrongStack, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in packages/core/skills/design-to-code of WrongStack/WrongStack.
Open the folder on GitHubat commit a744bdc
Compare with similar skills
Design To Code 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 To Code this skillWrongStack/WrongStack | 371 | — | ~800 | Automated safety check: Pass | MIT | |
| Figma use_figma Plugin API Ruleswarpdotdev/warp | 65k | 4 repos | ~4.4k | Automated safety check: Pass | AGPL-3.0 | |
| Figma Design to Codewarpdotdev/warp | 65k | 4 repos | ~2.9k | Automated safety check: Pass | AGPL-3.0 | |
| Figma Design System Rules Generatorwarpdotdev/warp | 65k | 3 repos | ~4.6k | Automated safety check: Pass | AGPL-3.0 | |
| Figma Code Connect Componentswarpdotdev/warp | 65k | 2 repos | ~4.2k | Automated safety check: Pass | AGPL-3.0 | |
| Design To CodeMigoXLab/coderio | 114 | 2 repos | ~1.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Figma Design to Code
warpdotdev/warp
Turns a Figma frame or component into production code that matches the design, using the Figma MCP server and the project's own design system.
Figma Design System Rules Generator
warpdotdev/warp
Creates project-specific design system rules from your codebase so coding agents implement Figma designs with your components, naming and tokens.
Figma Code Connect Components
warpdotdev/warp
Maps published Figma components to their code implementations with Code Connect, using the Figma MCP suggestion and mapping tools.
Design To Code
MigoXLab/coderio
Pixel-perfect Figma to React conversion using coderio. An agent skill from MigoXLab/coderio.
Figma Screen Generator
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.
More from WrongStack/WrongStack
All 100 skills in this repoTech Stack
WrongStack/WrongStack
Validate and upgrade dependencies against live registries and official migration guides in any ecosystem.
Skill Creator
WrongStack/WrongStack
Create, improve and validate WrongStack SKILL.md bundles with precise discovery, progressive resources and current runtime contracts.
Bug Hunter
WrongStack/WrongStack
A skill your agent uses when scanning source code for bugs, anti-patterns, code smells, or quality issues in a codebase, or when running a proof-driven bug hunt that must find, prove, fix, and…
Design Craft
WrongStack/WrongStack
Design or substantially improve user-facing interfaces with a product-specific visual direction, content hierarchy, and rendered critique.
Design Critique
WrongStack/WrongStack
A skill your agent uses to audit an interface that already exists and say precisely why it looks generated, templated, or unfinished — a scored rubric across composition, typography, color, states…
Mailbox Bridge
WrongStack/WrongStack
A skill your agent uses when external coding agents (Claude Code, Aider, custom scripts) need to participate in the project's shared WrongStack mailbox, or when a user asks to "expose the mailbox"…
Related
Works with
Categories
Questions about Design To Code
What does Design To Code do?
Implement supplied Figma designs, screenshots or design specifications as working interfaces. Design To Code is an agent skill from WrongStack/WrongStack. Implement supplied Figma designs, screenshots or design specifications as working interfaces.
When should I use Design To Code?
Design To Code fits situations like: matching a reference; handling design handoff; inspect the actual artifact and preserve its layout; content and interaction intent.
How do I install Design To Code in Claude Code?
Run `npx skills add WrongStack/WrongStack --skill design-to-code -a claude-code`. Or copy the skill folder (packages/core/skills/design-to-code in WrongStack/WrongStack) into .claude/skills/design-to-code in your project. Claude Code loads it when a task matches its description.
How do I install Design To Code in Codex?
Run `npx skills add WrongStack/WrongStack --skill design-to-code -a codex`. Or copy the skill folder (packages/core/skills/design-to-code in WrongStack/WrongStack) into .agents/skills/design-to-code in your project. Codex loads it when a task matches its description.
Can I use Design To Code in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add WrongStack/WrongStack --skill design-to-code -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-to-code, .gemini/skills/design-to-code, .github/skills/design-to-code and .opencode/skills/design-to-code in your project.
What does Design To Code need to run?
SKILL.md names no scripts, command-line tools or credentials: Design To Code is instructions for the agent only.
Does Design To Code access the network?
SKILL.md names 2 domains. As links in the text: developers.figma.com and developer.mozilla.org. This is read from the text; nothing was executed.
Is Design To Code safe to install?
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.
What licence does Design To Code use?
Design To Code is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Design To Code use?
About 800 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Design To Code?
Skills that share tags, products or a category with Design To Code: Figma use_figma Plugin API Rules (warpdotdev/warp, 65k stars), Figma Design to Code (warpdotdev/warp, 65k stars), Figma Design System Rules Generator (warpdotdev/warp, 65k stars) and Figma Code Connect Components (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Design To Code?
WrongStack (a GitHub organization) maintains it in WrongStack/WrongStack, which has 371 GitHub stars. The repository holds 100 skills in this directory. The repository was last updated on October 10, 2026.
Source: WrongStack/WrongStack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.