Figma Implement Component

What it does

When your agent uses it

• Phrases like build this component from Figma
• Implement this design
• Create a component from this Figma URL
• Turn this Figma into code

Example prompts

• “build this component from Figma”
• “implement this design”
• “create a component from this Figma URL”
• “/figma-implement-component”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

1. 1Verifies design analysis exists (or triggers it)
2. 2Creates component modlet following project standards
3. 3Writes README with Figma source and mapping context
4. 4Implements the component matching Figma design precisely
5. 5Creates Storybook stories for each Figma variant/state
6. 6Verifies tests pass and Storybook renders

What it can do on your machine

Read from SKILL.md and the folder at commit df229b1. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • npm

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Figma Implement Component loads about 1.8k tokens when it runs. Until then it costs about 130 tokens; SKILL.md has 599 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~130

When it runs · the whole SKILL.md, loaded when a task matches

~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from bitovi/ai-enablement-prompts at commit df229b1, republished under its MIT licence (© bitovi). 599 words, ~1,780 tokens.

name

figma-implement-component

description

Implement React components from Figma designs. Use after figma-design-react has analyzed the design, or directly with a Figma URL to run analysis and implementation in one shot. Delegates to create-react-modlet for folder structure, then adds Figma-specific implementation, stories for each variant, and README with design context. Also triggers on phrases like "build this component from Figma", "implement this design", "create a component from this Figma URL", "turn this Figma into code".

argument-hint

<figma-url>

user-invocable

true

┌─────────────────────────────────────────────────────────────────┐
│ 0. CREATE TODO LIST - Track all steps systematically           │
├─────────────────────────────────────────────────────────────────┤
│ 1. VERIFY AND GENERATE - Check for design analysis files       │
│    → If missing: Invoke figma-design-react skill                │
│    → Creates .temp/design-components/{name}/design-context.md   │
│    → Creates .temp/design-components/{name}/proposed-api.md     │
├─────────────────────────────────────────────────────────────────┤
│ 2. CREATE MODLET - Build folder structure using modlet pattern │
├─────────────────────────────────────────────────────────────────┤
│ 3. WRITE README - Document Figma source and mapping rationale  │
├─────────────────────────────────────────────────────────────────┤
│ 4. CREATE TYPES - Define TypeScript props interface            │
├─────────────────────────────────────────────────────────────────┤
│ 5. IMPLEMENT - Build component matching Figma precisely        │
├─────────────────────────────────────────────────────────────────┤
│ 6. CREATE STORIES - Story for each Figma variant/state         │
├─────────────────────────────────────────────────────────────────┤
│ 7. CREATE TESTS - Unit tests for all variants and behaviors    │
├─────────────────────────────────────────────────────────────────┤
│ 8. UPDATE EXPORTS - Add to index.ts                             │
├─────────────────────────────────────────────────────────────────┤
│ 9. VERIFY - Run tests, check types, confirm Storybook renders  │
├─────────────────────────────────────────────────────────────────┤
│ 10. PLAYWRIGHT - Visual test Storybook against Figma design    │
└─────────────────────────────────────────────────────────────────┘

© bitovi, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 13 other files in figma/figma-implement-component of bitovi/ai-enablement-prompts.

• SKILL.md
• reference/output-files.md
• reference/quality-checklist.md
• steps/00-todo-setup.md
• steps/01-design-analysis.md
• steps/02-modlet-structure.md
• steps/03-readme.md
• steps/04-types.md
• steps/05-implementation.md
• steps/06-stories.md
• steps/08-tests.md
• steps/09-exports.md
• steps/10-verification.md
• steps/11-playwright.md

Open the folder on GitHubat commit df229b1