Skip to content
Back to skills

Figma Design Workflow

ASecurity

Figma MCP workflow \u2014 extract designs, convert to code, Code Connect mappings, design tokens. Triggers on Figma URLs

  • 6 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 6, 2026
ai-agentstypescriptgoreactnodefrontend

Works with

  • cli
  • mcp

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned September 6, 2026

npx -y skills add ArieGoldkin/claude-forge --skill figma-design-workflow --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Figma Design Workflow?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Figma Design Workflow
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ariegoldkin-figma-design-workflow/badge)](https://www.skillsdirectory.com/skills/ariegoldkin-figma-design-workflow)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: figma-design-workflow
description: "Figma MCP workflow \u2014 extract designs, convert to code, Code Connect mappings, design tokens. Triggers on Figma URLs"
effort: medium
paths:
  - "**/*.tsx"
  - "**/*.jsx"
  - "**/*.css"
  - "**/*.figma"
---

# Figma Design Workflow

Select the right Figma MCP tool and follow efficient design-to-code patterns.

## Tool Selection

| Goal | Tool |
|------|------|
| Get code from design | `get_design_context` (primary) |
| Visual reference | `get_screenshot` |
| Explore structure | `get_metadata` |
| Extract design tokens | `get_variable_defs` |
| Map code to Figma | `add_code_connect_map` |
| Check existing mappings | `get_code_connect_map` |
| FigJam boards | `get_figjam` |
| Create diagrams | `generate_diagram` |
| Debug auth | `whoami` |

**For decision tree:** See `${CLAUDE_SKILL_DIR}/references/tool-selection-guide.md`

## URL Parsing

```
https://figma.com/design/:fileKey/:fileName?node-id=:nodeId

Example: https://figma.com/design/abc123/MyDesign?node-id=1966-17723
         fileKey = "abc123"
         nodeId = "1966:17723"  (convert hyphen to colon)
```

**Branch URLs:** Use `branchKey` as fileKey:
```
https://figma.com/design/:fileKey/branch/:branchKey/:fileName
```

## Typical Workflow

1. **Parse URL** → Extract fileKey and nodeId
2. **Screenshot** → `get_screenshot` for visual reference
3. **Design context** → `get_design_context` for code
4. **Variables** → `get_variable_defs` for design tokens
5. **Implement** → Use `prototype-to-production` skill for conversion
6. **Map** → `add_code_connect_map` to link component

## Quick Examples

```typescript
// Get code from design
mcp__Figma__get_design_context({
  fileKey: "abc123",
  nodeId: "1966:17723",
  clientLanguages: "typescript",
  clientFrameworks: "react"
})

// Extract design tokens
mcp__Figma__get_variable_defs({
  fileKey: "abc123",
  nodeId: "1966:17723"
})

// Map component to Figma
mcp__Figma__add_code_connect_map({
  fileKey: "abc123",
  nodeId: "1966:17723",
  source: "src/components/ui/button.tsx",
  componentName: "Button",
  label: "React"
})
```

## Integration

- **`prototype-to-production`**: Pass `get_design_context` output for component decomposition and TypeScript generation
- **`frontend-creative-design`**: Use extracted tokens for creative direction

## References

- `${CLAUDE_SKILL_DIR}/references/tool-selection-guide.md` - Detailed decision tree with examples
- `${CLAUDE_SKILL_DIR}/references/common-patterns.md` - Batch operations, token extraction workflow

Files in this skill

  • SKILL.md2.5 KB
  • references/common-patterns.md3.9 KB
  • references/tool-selection-guide.md3.4 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.