Agent skill · Data & Analytics

figma-implement-design

Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Use when the user provides Figma URLs or node IDs and asks to implement designs or components that must match Figma specs. Requires a working Figma MCP server connection. Do NOT use for general Figma data fetching, variable exploration, or MCP troubleshooting (use figma instead).

tech-leads-clubgithub.com/tech-leads-clubGitHub ↗
claude-codecopilotcursorNOASSERTION
Install
npx skills add tech-leads-club/agent-skills --skill figma-implement-design --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 11 KB
Bundled scripts: none
Version: 1.0.0
Declared author: github.com/openai/skills
Path: packages/skills-catalog/skills/(design)/figma-implement-design/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 4,983
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Implement Design ## Overview This skill provides a structured workflow for translating Figma designs into production-ready code with pixel-perfect accuracy. It ensures consistent integration with the Figma MCP server, proper use of design tokens, and 1:1 visual parity with designs. ## Prerequisites - Figma MCP server must be connected and accessible - User must provide a Figma URL in the format: `https://figma.com/design/:fileKey/:fileName?node-id=1-2` - `:fileKey` is the file key - `1-2` is the node ID (the specific component or frame to implement) - **OR** when using `figma-desktop` MCP: User can select a node directly in the Figma desktop app (no URL required) - Project should have an established design system or component library (preferred) ## Required Workflow **Follow these steps in order. Do not skip steps.** ### Step 0: Set up Figma MCP (if not already configured) If any MCP call fails because Figma MCP is not connected, pause and set it up: 1. Add the Figma MCP server to your agent's MCP configuration: - URL: `https://mcp.figma.com/mcp` 2. Enable remote MCP client if required by your agent. 3. Log in with OAuth following your agent's authentication flow. After successfu

What's inside
Steps it walks through
  1. Overview
  2. Prerequisites
  3. Required Workflow
  4. Step 0: Set up Figma MCP (if not already configured)
  5. Step 1: Get Node ID
  6. Step 2: Fetch Design Context
  7. Step 3: Capture Visual Reference
  8. Step 4: Download Required Assets
  9. Step 5: Translate to Project Conventions
  10. Step 6: Achieve 1:1 Visual Parity
  11. Step 7: Validate Against Figma
  12. Implementation Rules
  13. Component Organization
  14. Design System Integration
Ships with 1 file
  • LICENSE.txt
More from agent-skills
All skills →
About this skill
What does the figma-implement-design skill do?

Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Use when the user provides Figma URLs or node IDs and asks to implement designs or components that must match Figma specs. Requires a working Figma MCP server connection. Do NOT use for general Figma data fetching, variable exploration, or MCP troubleshooting (use figma instead).

How do I install it?

Run `npx skills add tech-leads-club/agent-skills --skill figma-implement-design --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From tech-leads-club/agent-skills, a repository with 4,983 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going