| name | figma-api |
| description | Direct Figma API interactions for design asset management. Fetch files and components, extract design tokens, export images, manage comments, and access version history. |
| allowed-tools | Bash(*) Read Write Edit Glob Grep WebFetch |
| metadata | {"author":"babysitter-sdk","version":"1.0.0","category":"design-integration","backlog-id":"SK-UX-002"} |
| graph | {"domains":["domain:web-development"],"specializations":["specialization:ux-ui-design"],"skillAreas":["skill-area:figma-prototyping","skill-area:design-systems"],"roles":["role:product-designer"],"workflows":["workflow:user-feedback-loop","workflow:product-discovery"]} |
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:
const fileData = await figmaApi.getFile(fileKey);
const nodes = await figmaApi.getFileNodes(fileKey, ['1:2', '1:3']);
const components = await figmaApi.getComponents(fileKey);
const componentSets = await figmaApi.getComponentSets(fileKey);
2. Design Token Extraction
Extract design tokens from Figma files:
{
"colors": {
"primary": {
"50": { "value": "#E3F2FD", "type": "color" },
"100": { "value": "#BBDEFB", "type": "color" },
"500": { "value": "#2196F3", "type": "color" },
"900": { "value": "#0D47A1", "type": "color" }
},
"semantic": {
3. Image Export
Export images and assets at various scales:
const images = await figmaApi.getImage(fileKey, {
ids: ['1:2', '1:3'],
format: 'png',
scale: 2
});
const svgImages = await figmaApi.getImage(fileKey, {
ids: ['1:4'],
format: 'svg',
svg_include_id: true,
svg_simplify_stroke: true
});
const renderedImages = await figmaApi.getImageFills(fileKey);
4. Comment Management
Manage design feedback and comments:
const comments = await figmaApi.getComments(fileKey);
const newComment = await figmaApi.postComment(fileKey, {
message: 'Please review the button states',
client_meta: { x: 100, y: 200 }
});
const reply = await figmaApi.postComment(fileKey, {
message: 'Updated per feedback',
comment_id: '123456'
});
await figmaApi.deleteComment(fileKey, commentId);
5. Version History
Access file version history:
const versions = await figmaApi.getVersions(fileKey);
{
"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:
const styles = await figmaApi.getStyles(fileKey);
const colorStyles = styles.filter(s => s.style_type === 'FILL');
const textStyles = styles.filter(s => s.style_type === 'TEXT');
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 |
| Figma MCP Server (karthiks3000) | Claude MCP Server for working with Figma files | GitHub |
| html.to.design MCP | Converts HTML directly into editable Figma designs | Docs |
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
curl -H "X-Figma-Token: YOUR_TOKEN" \
"https://api.figma.com/v1/files/FILE_KEY"
curl -H "Authorization: Bearer OAUTH_TOKEN" \
"https://api.figma.com/v1/files/FILE_KEY"
Best Practices
- Cache responses - Figma API has rate limits; cache file data locally
- Use node IDs - Fetch specific nodes instead of entire files when possible
- Batch exports - Group image exports to minimize API calls
- Handle pagination - Large files may require paginated requests
- Version your tokens - Use descriptive names and rotate tokens regularly
- 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:
{
"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