figma-to-code
Repo-first Figma-to-code workflow for implementation, design tokens, design-system rules, and Code Connect. Use when the user asks to "implement this Figma design", "turn this Figma into code", "build from a Figma link", "match this Figma mockup", "extract Figma design tokens", "create Figma design system rules", "set up Figma guidelines", "code connect this component", or "map this Figma component to code"; or when a Figma URL/selection must become repository code, code tokens, agent rules, or Code Connect mappings.
73
90%
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.
1 low severity finding. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
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.
Why it was flagged
The required runtime workflow for `/figma-to-code implement` fetches and ingests untrusted Figma design data via MCP tools like `get_design_context`, `get_metadata`, `get_variable_defs`, and `get_screenshot` (including layer text/content and generated code snippets), so an outsider can poison the Figma design text that the agent reads.
- Repository
- t4sh/skills4sh
- Commit
3858600
- Audited
- Security analysis
Is this your skill?
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.