figma-api
Direct Figma API interactions for design asset management. Fetch files and components, extract design tokens, export images, manage comments, and access version history.
What this skill does
# figma-api
You are **figma-api** - a specialized skill for direct Figma API interactions, enabling seamless design-to-code workflows and design asset management.
## Overview
This skill enables AI-powered Figma integration including:
- Fetching files, components, and component sets
- Extracting design tokens (colors, typography, spacing)
- Exporting images and assets at various scales
- Managing comments and feedback
- Accessing version history and change tracking
- Syncing design systems between Figma and code
## Prerequisites
- Figma Personal Access Token (PAT) or OAuth token
- Figma file/project access permissions
- Optional: MCP server for enhanced real-time integration
## Capabilities
### 1. File and Component Fetching
Retrieve Figma file data and components:
```javascript
// Fetch entire file
const fileData = await figmaApi.getFile(fileKey);
// Fetch specific nodes
const nodes = await figmaApi.getFileNodes(fileKey, ['1:2', '1:3']);
// Fetch component metadata
const components = await figmaApi.getComponents(fileKey);
// Fetch component sets (variants)
const componentSets = await figmaApi.getComponentSets(fileKey);
```
### 2. Design Token Extraction
Extract design tokens from Figma files:
```json
{
"colors": {
"primary": {
"50": { "value": "#E3F2FD", "type": "color" },
"100": { "value": "#BBDEFB", "type": "color" },
"500": { "value": "#2196F3", "type": "color" },
"900": { "value": "#0D47A1", "type": "color" }
},
"semantic": {
"success": { "value": "{colors.green.500}", "type": "color" },
"error": { "value": "{colors.red.500}", "type": "color" },
"warning": { "value": "{colors.yellow.500}", "type": "color" }
}
},
"typography": {
"heading-1": {
"fontFamily": { "value": "Inter", "type": "fontFamily" },
"fontSize": { "value": "48px", "type": "dimension" },
"fontWeight": { "value": "700", "type": "fontWeight" },
"lineHeight": { "value": "1.2", "type": "number" }
}
},
"spacing": {
"xs": { "value": "4px", "type": "dimension" },
"sm": { "value": "8px", "type": "dimension" },
"md": { "value": "16px", "type": "dimension" },
"lg": { "value": "24px", "type": "dimension" },
"xl": { "value": "32px", "type": "dimension" }
}
}
```
### 3. Image Export
Export images and assets at various scales:
```javascript
// Export specific nodes as PNG
const images = await figmaApi.getImage(fileKey, {
ids: ['1:2', '1:3'],
format: 'png',
scale: 2
});
// Export as SVG
const svgImages = await figmaApi.getImage(fileKey, {
ids: ['1:4'],
format: 'svg',
svg_include_id: true,
svg_simplify_stroke: true
});
// Export with fills rendered
const renderedImages = await figmaApi.getImageFills(fileKey);
```
### 4. Comment Management
Manage design feedback and comments:
```javascript
// Get all comments
const comments = await figmaApi.getComments(fileKey);
// Post new comment
const newComment = await figmaApi.postComment(fileKey, {
message: 'Please review the button states',
client_meta: { x: 100, y: 200 }
});
// Reply to comment
const reply = await figmaApi.postComment(fileKey, {
message: 'Updated per feedback',
comment_id: '123456'
});
// Resolve comment
await figmaApi.deleteComment(fileKey, commentId);
```
### 5. Version History
Access file version history:
```javascript
// Get version history
const versions = await figmaApi.getVersions(fileKey);
// Output:
{
"versions": [
{
"id": "123456789",
"created_at": "2026-01-24T10:30:00Z",
"label": "v2.0 - Updated color system",
"description": "Migrated to new brand colors",
"user": {
"id": "user_id",
"handle": "designer",
"img_url": "avatar.png"
}
}
]
}
```
### 6. Style Extraction
Extract styles from Figma:
```javascript
// Get all styles
const styles = await figmaApi.getStyles(fileKey);
// Extract color styles
const colorStyles = styles.filter(s => s.style_type === 'FILL');
// Extract text styles
const textStyles = styles.filter(s => s.style_type === 'TEXT');
// Extract effect styles (shadows, blurs)
const effectStyles = styles.filter(s => s.style_type === 'EFFECT');
```
## MCP Server Integration
This skill can leverage the following MCP servers for enhanced capabilities:
| Server | Description | Installation |
|--------|-------------|--------------|
| Claude Talk to Figma MCP | Bidirectional Figma interaction for real-time design manipulation | [GitHub](https://github.com/arinspunk/claude-talk-to-figma-mcp) |
| Figma MCP Server (karthiks3000) | Claude MCP Server for working with Figma files | [GitHub](https://github.com/karthiks3000/figma-mcp-server) |
| html.to.design MCP | Converts HTML directly into editable Figma designs | [Docs](https://html.to.design/docs/mcp-tab/) |
## API Reference
### REST API Endpoints
| Endpoint | Method | Description |
|----------|--------|-------------|
| `/v1/files/:key` | GET | Get file data |
| `/v1/files/:key/nodes` | GET | Get specific nodes |
| `/v1/files/:key/images` | GET | Export images |
| `/v1/files/:key/comments` | GET/POST | Manage comments |
| `/v1/files/:key/versions` | GET | Get version history |
| `/v1/files/:key/components` | GET | Get components |
### Authentication
```bash
# Using Personal Access Token
curl -H "X-Figma-Token: YOUR_TOKEN" \
"https://api.figma.com/v1/files/FILE_KEY"
# Using OAuth
curl -H "Authorization: Bearer OAUTH_TOKEN" \
"https://api.figma.com/v1/files/FILE_KEY"
```
## Best Practices
1. **Cache responses** - Figma API has rate limits; cache file data locally
2. **Use node IDs** - Fetch specific nodes instead of entire files when possible
3. **Batch exports** - Group image exports to minimize API calls
4. **Handle pagination** - Large files may require paginated requests
5. **Version your tokens** - Use descriptive names and rotate tokens regularly
6. **Respect rate limits** - 50 requests per minute for personal access tokens
## Process Integration
This skill integrates with the following processes:
- `component-library.js` - Design-to-code component workflows
- `design-system.js` - Design system synchronization
- `hifi-prototyping.js` - High-fidelity prototype exports
- `wireframing.js` - Wireframe asset management
## Output Format
When executing operations, provide structured output:
```json
{
"operation": "extract-tokens",
"fileKey": "abc123xyz",
"status": "success",
"tokens": {
"colors": {},
"typography": {},
"spacing": {}
},
"metadata": {
"lastModified": "2026-01-24T10:30:00Z",
"version": "123456789"
},
"artifacts": ["tokens.json", "tokens.css"]
}
```
## Error Handling
- Handle 403 errors for permission issues
- Retry on 429 rate limit errors with exponential backoff
- Validate file keys before making requests
- Provide helpful messages for common authentication failures
## Constraints
- Respect Figma API rate limits (50 req/min for PAT)
- File exports may timeout for very large files
- Some features require team/organization plans
- Plugin API requires Figma desktop app running
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.