Figma Design To Code

CommunityPopular

Devin-AXIS

figma-design-to-code

Use this skill when implementing a Figma design as code (design → code) — the read-FROM-Figma direction. Triggers: 'implement this Figma design', 'build this screen from Figma', 'turn this Figma into code', 'code this up from Figma', 'design to code', or a figma.com design URL provided alongside a codebase. Encodes the workflow for reading a node out of Figma with get_design_context and adapting its reference output to the target project — reusing existing components, tokens, and conventions, and honoring Code Connect mappings, component docs, design annotations, and design tokens by priority. Complements figma-code-connect (component mapping) and figma-generate-design / figma-use (the reverse, code → design direction).

Overview

Publisher	Devin-AXIS
Repository	`iPolloWork`
Skill name	`figma-design-to-code`
Stars	6.3K
Forks	1.2K
Bundled files	Instructions only
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by Devin-AXIS on GitHub. Read the source before you install it.

Installation

Install the Figma Design To Code AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/Devin-AXIS/iPolloWork/tree/main/examples/plugin-packages/figma/skills/figma-design-to-code

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork.git /tmp/iPolloWork
mkdir -p .claude/skills
cp -r /tmp/iPolloWork/examples/plugin-packages/figma/skills/figma-design-to-code .claude/skills/figma-design-to-code

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Figma Design To Code in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Figma Design To Code on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Figma Design To Code is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Implement a Figma Design as Code (Design → Code)

Use this skill to turn a Figma design into code in a target codebase. This is the read-FROM-Figma direction: pull design context out of Figma with get_design_context, then adapt it into the project's real stack. For the reverse direction — building or updating a design in Figma from code — use figma-generate-design instead.

This skill owns the workflow for design-to-code. Parameter mechanics (nodeId / fileKey / branchKey extraction, URL parsing, format/query options, response shape) live on the get_design_context tool description itself — follow them there.

Direction and Scope

You MUST use this skill for design → code: implementing, translating, or porting a Figma node into code.
You MUST NOT use this skill to write to Figma.

Workflow

1. Call get_design_context first

You MUST call get_design_context on the target node before writing any code. It is your primary tool — a single call returns reference code, a screenshot, and contextual hints.
You MUST NOT reach for get_metadata or get_screenshot as a substitute. Use them only to orient (e.g. picking a node) or to validate, not in place of get_design_context.

2. Treat the output as a reference, not final code

The returned code is React + Tailwind enriched with hints. You MUST treat it as a REFERENCE, not as final code to paste verbatim.
You MUST adapt it to the target project's language, framework, component library, styling system, and conventions. Match the surrounding code.

3. Reuse what the project already has

Before writing new code, You MUST check the target project for existing components, layout patterns, and design tokens that match the design intent.
You MUST reuse the project's existing components and tokens instead of generating new equivalents from scratch.

4. Honor the response hints by priority

Apply the hints in this order — earlier sources override later ones:

Code Connect snippets → use the mapped codebase component directly.
Component documentation links → follow them for usage and guidelines.
Design annotations → follow any designer notes or constraints.
Design tokens (CSS variables) → map them to the project's token system.
Raw hex / absolute positioning → loosely structured; lean on the screenshot for intent.

Error Recovery

On a get_design_context error, STOP and read the message before retrying.
If the design URL has no node-id (a file-only URL), ask the user for a node-specific URL — You MUST NOT guess or pass an empty nodeId.
On a timeout, retry against a smaller node or selection.
You MUST NOT silently fall back to hand-writing the screen from the screenshot alone when get_design_context can still provide context.

Frequently asked questions

What does the Figma Design To Code AI skill do?

Why use Figma Design To Code on TypingMind?

Because you install it once and use it with any model. Figma Design To Code is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Figma Design To Code in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Devin-AXIS/iPolloWork/tree/main/examples/plugin-packages/figma/skills/figma-design-to-code. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Figma Design To Code?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Figma Design To Code?

As many as you like. As long as a model supports skills, you can use Figma Design To Code with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Figma Design To Code AI skill free?

It is published on GitHub by Devin-AXIS. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Design Shotgun

garrytan

CommunityPopular

Design shotgun: generate multiple AI design variants, open a comparison board, collect structured feedback, and iterate. (gstack)

Diagram

Turn an English description (or mermaid source) into a diagram triplet: the source, an editable .excalidraw file you can open on excalidraw.com, and rendered SVG + PNG. (gstack)

Office Hours

YC Office Hours — two modes. (gstack)

Plan Design Review

Designer's eye plan review — interactive, like CEO and Eng review. (gstack)

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Implement a Figma Design as Code (Design → Code)

Direction and Scope

Workflow

1. Call get_design_context first

2. Treat the output as a reference, not final code

3. Reuse what the project already has

4. Honor the response hints by priority

Error Recovery

Frequently asked questions

Related AI Skills

Set up your own AI workspace now