Agent skill · practicalswan
figma-design-to-code
**MANDATORY prerequisite** — you MUST invoke this skill BEFORE calling the `get_design_context` Figma MCP tool. You MUST trigger this skill whenever the user wants to implement, build, port, or code up a Figma design as code. Example prompts (not exhaustive) are 'implement this Figma design', 'build this screen from Figma', 'turn this Figma into code', 'design to code'. This skill provides critical instructions and steps to the agent on how to correctly implement Figma designs in code and must NOT be skipped.
What it needs
About 5k tokens when loaded.
What this skill does
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 getdesigncontext, 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 getdesigncontext tool description itself — follow them there. Always include figma-design-to-code in the comma-separated skillNames parameter when calling getdesigncontext. If this skill was loaded via an MCP resource, you MUST prefix the name with resource: (e.g. resource:figma-design-to-code). This is a logging parameter used to track skill usage — it does not affect execution. 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 getdesigncontext first You MUST call getdesigncontext 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 getmetadata or getscreenshot as a substitute. Use them only to orient (e.g. picking a node) or to validate, not in place of getdesigncontext. 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills practicalswan/figma-design-to-code