figma-design

Extract design specs, tokens, and screenshots from Figma frames via MCP or REST API.

Updated Jul 5, 2026
One-click install
npx skills add https://github.com/wem2017/agent-flow-plugin --skill figma-design-wem2017
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: figma-design
Source: https://github.com/wem2017/agent-flow-plugin/tree/main/agentflow/skills/figma-design
Command: npx skills add https://github.com/wem2017/agent-flow-plugin --skill figma-design-wem2017

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers implementing UI from Figma designs need a reliable way to pull structured design context, design tokens, and visual references from a specific frame without manually inspecting the file or pasting raw generated code into their codebase. ## Core Features & Use Cases - Dual access paths: Uses the official Figma MCP server over OAuth as the preferred path, with a PAT-based REST API fallback (X-Figma-Token header) for headless or enterprise setups. - Structured extraction tools: get_metadata for cheap node discovery, get_design_context for design-to-code context, get_variable_defs for color/spacing/typography tokens, get_screenshot for visual diffing, and get_code_connect_map to reuse real mapped components. - URL and node-id parsing: Extracts FILE_KEY from /design/ or /file/ URLs, handles branch URLs, and converts node-id dash format to colon format required by both MCP and REST. - Use Case: Given an acceptance criterion referencing a Figma frame URL, pull the frame's structured context and variable definitions, map tokens to the project's existing design system, and capture a screenshot to verify the implemented layout. ## Quick Start Extract the design context, tokens, and a screenshot from this Figma frame URL so I can implement it with our existing components.

Frequently Asked Questions about figma-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract design specs from a Figma frame URL?

Parse the FILE_KEY from the path segment after /design/ and the node-id from the URL query, then call get_design_context on the official Figma MCP server with the URL or explicit nodeId. Convert node-id dashes to colons when passing nodeId explicitly.

Official Figma MCP server vs REST API with personal access token?

The official MCP server authenticates via OAuth and provides structured tools like get_design_context and get_variable_defs, making it the preferred path. The REST API with a FIGMA_TOKEN in the X-Figma-Token header is a fallback for headless setups and is the only path that returns real file version revisions.

Why does Figma return an invalid node ID error?

URLs express node-id with dashes (1234-5678) but both the MCP server and REST API require colon format (1234:5678). Convert with NODE_ID="${URL_NODE_ID//-/:}" before passing the ID explicitly.

Can the agent modify or write to Figma files?

No. Only read methods are used; write tools exposed by the remote server (creating files, generating designs, uploading assets) are never called. The design is a human-owned source of truth that QC relies on for verification.

How do I pin a Figma design revision for verification?

The REST endpoints /v1/files/$FILE_KEY and /nodes return a top-level version and lastModified, and ?version=<id> pins that exact revision. Note version is file-level, so compare node content before concluding the design changed.