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). Trigger when the user provides Figma URLs or node IDs, or asks to implement designs or components that must match Figma specs. Requires a working Figma MCP server connection.
75
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Low
Low-risk findings.
2 low severity findings. Worth noting, but not necessarily harmful.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The required workflow calls Figma MCP tools (`get_design_context`, `get_metadata`, `get_screenshot`, and downloads assets) using user-supplied Figma links/selections, meaning outsider-authored Figma content is fetched at runtime and becomes readable LLM context for implementation.
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
The Figma MCP endpoint https://mcp.figma.com/mcp is a required runtime tool endpoint (declared in agents/openai.yaml and referenced in SKILL.md and config) whose responses (design context and generated code snippets) are fetched at runtime and injected into the agent's workflow, so the external content can directly control the agent's outputs.
f627ab5
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.