Claude Cursor opencode Skill

figma

Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download vodailocz-kilo-kit-mcp-skills_design_figma-0448e6c.zip · 11 KB

Install

skills CLI npx skills add https://github.com/VoDaiLocz/kilo-kit-mcp/tree/main/skills/design/figma
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install vodailocz-kilo-kit-mcp@llmmart
Git git clone https://github.com/VoDaiLocz/kilo-kit-mcp.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole vodailocz/kilo-kit-mcp collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Figma MCP

Use the Figma MCP server for Figma-driven implementation. For setup and debugging details (env vars, config, verification), see references/figma-mcp-config.md.

Figma MCP Integration Rules

These rules define how to translate Figma inputs into code for this project and must be followed for every Figma-driven change.

Required flow (do not skip)

  1. Run get_design_context first to fetch the structured representation for the exact node(s).
  2. If the response is too large or truncated, run get_metadata to get the high-level node map and then re-fetch only the required node(s) with get_design_context.
  3. Run get_screenshot for a visual reference of the node variant being implemented.
  4. Only after you have both get_design_context and get_screenshot, download any assets needed and start implementation.
  5. Translate the output (usually React + Tailwind) into this project's conventions, styles and framework. Reuse the project's color tokens, components, and typography wherever possible.
  6. Validate against Figma for 1:1 look and behavior before marking complete.

Implementation rules

  • Treat the Figma MCP output (React + Tailwind) as a representation of design and behavior, not as final code style.
  • Replace Tailwind utility classes with the project's preferred utilities/design-system tokens when applicable.
  • Reuse existing components (e.g., buttons, inputs, typography, icon wrappers) instead of duplicating functionality.
  • Use the project's color system, typography scale, and spacing tokens consistently.
  • Respect existing routing, state management, and data-fetch patterns already adopted in the repo.
  • Strive for 1:1 visual parity with the Figma design. When conflicts arise, prefer design-system tokens and adjust spacing or sizes minimally to match visuals.
  • Validate the final UI against the Figma screenshot for both look and behavior.

Asset handling

  • The Figma MCP Server provides an assets endpoint which can serve image and SVG assets.
  • IMPORTANT: If the Figma MCP Server returns a localhost source for an image or an SVG, use that image or SVG source directly.
  • IMPORTANT: DO NOT import/add new icon packages, all the assets should be in the Figma payload.
  • IMPORTANT: do NOT use or create placeholders if a localhost source is provided.

Link-based prompting

  • The server is link-based: copy the Figma frame/layer link and give that URL to the MCP client when asking for implementation help.
  • The client cannot browse the URL but extracts the node ID from the link; always ensure the link points to the exact node/variant you want.

References

  • references/figma-mcp-config.md — setup, verification, troubleshooting, and link-based usage reminders.
  • references/figma-tools-and-prompts.md — tool catalog and prompt patterns for selecting frameworks/components and fetching metadata.
Files (kilo-kit-mcp)
  • agents
    • openai.yaml 460 B
      Loading…
  • assets
    • figma-small.svg 810 B · in bundle
    • figma.png 1.6 KB · in bundle
    • icon.svg 964 B · in bundle
  • references
    • figma-mcp-config.md 2.4 KB
      Loading…
    • figma-tools-and-prompts.md 2.7 KB
      Loading…
  • LICENSE.txt 11.1 KB
    Loading…
  • SKILL.md 3.1 KB
    ---
    name: figma
    description: Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.
    ---
    
    # Figma MCP
    
    Use the Figma MCP server for Figma-driven implementation. For setup and debugging details (env vars, config, verification), see `references/figma-mcp-config.md`.
    
    ## Figma MCP Integration Rules
    These rules define how to translate Figma inputs into code for this project and must be followed for every Figma-driven change.
    
    ### Required flow (do not skip)
    1. Run get_design_context first to fetch the structured representation for the exact node(s).
    2. If the response is too large or truncated, run get_metadata to get the high-level node map and then re-fetch only the required node(s) with get_design_context.
    3. Run get_screenshot for a visual reference of the node variant being implemented.
    4. Only after you have both get_design_context and get_screenshot, download any assets needed and start implementation.
    5. Translate the output (usually React + Tailwind) into this project's conventions, styles and framework. Reuse the project's color tokens, components, and typography wherever possible.
    6. Validate against Figma for 1:1 look and behavior before marking complete.
    
    ### Implementation rules
    - Treat the Figma MCP output (React + Tailwind) as a representation of design and behavior, not as final code style.
    - Replace Tailwind utility classes with the project's preferred utilities/design-system tokens when applicable.
    - Reuse existing components (e.g., buttons, inputs, typography, icon wrappers) instead of duplicating functionality.
    - Use the project's color system, typography scale, and spacing tokens consistently.
    - Respect existing routing, state management, and data-fetch patterns already adopted in the repo.
    - Strive for 1:1 visual parity with the Figma design. When conflicts arise, prefer design-system tokens and adjust spacing or sizes minimally to match visuals.
    - Validate the final UI against the Figma screenshot for both look and behavior.
    
    ### Asset handling
    - The Figma MCP Server provides an assets endpoint which can serve image and SVG assets.
    - IMPORTANT: If the Figma MCP Server returns a localhost source for an image or an SVG, use that image or SVG source directly.
    - IMPORTANT: DO NOT import/add new icon packages, all the assets should be in the Figma payload.
    - IMPORTANT: do NOT use or create placeholders if a localhost source is provided.
    
    ### Link-based prompting
    - The server is link-based: copy the Figma frame/layer link and give that URL to the MCP client when asking for implementation help.
    - The client cannot browse the URL but extracts the node ID from the link; always ensure the link points to the exact node/variant you want.
    
    ## References
    - `references/figma-mcp-config.md` — setup, verification, troubleshooting, and link-based usage reminders.
    - `references/figma-tools-and-prompts.md` — tool catalog and prompt patterns for selecting frameworks/components and fetching metadata.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.