figma-context-mcp

Included with Lifetime

$97 forever

Expert guide for using the Figma Context MCP (Framelink) efficiently while avoiding 429 rate-limit errors. Activate when: (1) using Framelink Figma MCP tools (get_figma_data, download_figma_images), (2) fetching Figma designs for code generation, (3) user hits 429 rate limits from Figma API, (4) extracting design tokens or component data from Figma, (5) downloading Figma assets/images, (6) any design-to-code workflow involving Figma URLs. Covers metadata-first fetching, depth-limited node trees, batch image downloads, rate-limit diagnostics, and plan-tier awareness.

Design

What this skill does


# Figma Context MCP

Expert guide for the [Figma Context MCP](https://github.com/GLips/Figma-Context-MCP) (also known as Framelink). Teaches efficient API usage patterns that prevent 429 rate-limit lockouts.

## Tools

| Tool | Purpose | API Tier |
|------|---------|----------|
| `get_figma_data` | Fetch file/node structure, layout, components | Tier 1 (most restricted) |
| `download_figma_images` | Export PNG/SVG renders of specific nodes | Tier 2-3 |

## Critical: Rate Limits

Figma enforces per-plan rate limits. Limits apply based on the **file owner's plan**, not yours:

| Tier | Starter | Pro | Org |
|------|---------|-----|-----|
| Tier 1 (files) | 10/min | 15/min | 20/min |
| Tier 2 (images) | 25/min | 50/min | 100/min |
| Tier 3 | 50/min | 100/min | 150/min |

View/Collab seats get only **6 Tier-1 calls/month**. If accessing files owned by someone on a Starter/free plan, their limits apply to you.

429 lockouts can last **4-5 days**. Prevention is essential.

## Workflow: Metadata-First Pipeline

**Never fetch everything upfront.** Adopt this pipeline to keep most jobs under 2-3 API calls and <500 KB:

### 1. Start with a targeted node, not the whole file

When a user provides a Figma URL like `figma.com/design/FILEKEY/Name?node-id=123-456`, always extract and pass the `nodeId`. Never fetch the entire file when a specific node is available.

```
get_figma_data(fileKey="ABC123", nodeId="123-456", depth=2)
```

### 2. Use minimal depth

Always set `depth` to limit tree traversal:
- **depth=1**: Top-level frame only (layout structure, component names)
- **depth=2**: Frame + direct children (usually sufficient for code generation)
- **depth=3**: Maximum recommended — only when nested auto-layouts require it

**Default if omitted: the API returns the ENTIRE subtree** — often megabytes for complex frames with 50-200+ children. This is the #1 cause of 429 errors.

### 3. Analyze locally before fetching more

After receiving the initial response:
- Identify which child nodes actually need detail (skip hidden, decorative, or library-referenced nodes)
- Extract design tokens (colors, spacing, typography) directly from the response — no extra calls needed
- Build your component structure from what you already have

### 4. Fetch deeper nodes only if necessary

If a specific child node needs more detail, fetch just that node:

```
get_figma_data(fileKey="ABC123", nodeId="child-node-id", depth=1)
```

### 5. Download images last, in small batches

Only request images for the **final deduplicated set** of visual assets you actually need:
- Deduplicate by `imageRef` — multiple nodes can reference the same fill image
- Batch into groups of **5-10 nodes** per call
- Use `pngScale=1` unless the user specifically needs @2x/@3x assets

```
download_figma_images(
  fileKey="ABC123",
  nodes=[{nodeId: "1:2", fileName: "hero", ...}],  # max 5-10 per call
  localPath="./assets",
  pngScale=1
)
```

## When You Hit a 429

See [references/rate-limit-recovery.md](references/rate-limit-recovery.md) for diagnostics and recovery steps.

Quick checklist:
1. **Stop all Figma API calls immediately** — additional calls extend the lockout
2. Check if the file is owned by a Starter/free-plan user (limits are per-owner)
3. If the user has a Pro/Org plan, suggest duplicating the file into their own workspace
4. Wait for `Retry-After` header duration before retrying
5. When retrying, use the minimal-depth pipeline above

## Common Patterns

### Design-to-code (single component)
1. `get_figma_data` with specific `nodeId` + `depth=2` (1 call)
2. Generate code from response — no image calls unless the component contains raster assets
3. If images needed: `download_figma_images` for just the raster fills (1 call)
4. **Total: 1-2 API calls**

### Design-to-code (full page)
1. `get_figma_data` with page `nodeId` + `depth=1` to get frame list (1 call)
2. Identify the 2-3 key frames that matter
3. `get_figma_data` for each key frame with `depth=2` (2-3 calls)
4. Extract tokens locally, download only unique raster assets (1 call)
5. **Total: 4-5 API calls**

### Extract design tokens only
1. `get_figma_data` with `nodeId` + `depth=2` (1 call)
2. Parse colors, typography, spacing from the response — no image calls needed
3. **Total: 1 API call**

## Anti-Patterns

| Pattern | Problem | Fix |
|---------|---------|-----|
| Omitting `depth` | Returns entire subtree (MB of data) | Always set `depth=2` or less |
| Omitting `nodeId` | Fetches entire file | Always extract `nodeId` from URL |
| Downloading all images upfront | Bursts of image requests hit Tier 2 limits | Download only final deduplicated set |
| Retrying on 429 | Extends lockout duration | Stop, wait for `Retry-After`, then resume with minimal calls |
| Fetching library components | Remote library nodes trigger extra API calls | Use local component data from initial response |

Files: 2

Size: 8.5 KB

Complexity: 26/100

Category: Design

Source: https://github.com/vladmdgolam/agent-skills/tree/main/skills/figma-context-mcp

Related in Design

contribute

Included

Local-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".

Designscripts

architectural-analysis

Included

User-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).

Designscripts

mcp

Included

Model 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.

Designscripts

react-native-skia

Included

Design, 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.

Designscripts

plaid

Included

Product 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".

Designscripts

nextjs-framer-motion-animations

Included

Adds 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.

Designscripts