figma-developer
Extracts design data from Figma via the REST API and converts designs to React code. Use when syncing Figma tokens to CSS variables, exporting icons as SVG components, generating code from Figma designs, or automating design-to-code workflows. Use for design token extraction, icon export, component generation, and CI-based Figma sync.
What this skill does
# Figma Developer ## Overview Automates the Figma-to-code bridge using the Figma REST API. Extracts design tokens (colors, typography, spacing) as CSS variables and JSON, exports icons as SVG React components, generates React components from Figma node structures, and sets up CI pipelines for continuous design sync. **When to use:** Syncing design tokens from Figma to code, exporting icon sets as React components, generating component scaffolding from Figma variants, setting up automated design sync in CI. **When NOT to use:** Manual one-off design tweaks (just copy values), Figma plugin development (use the Plugin API instead), real-time collaborative editing (use Figma webhooks directly), or projects without a Figma design system. ## Quick Reference | Pattern | API / Approach | Key Points | | ------------------ | ------------------------------------------------------- | ---------------------------------------------------- | | Get file data | `GET /v1/files/:key` | Returns full document tree with styles and fills | | Get specific nodes | `GET /v1/files/:key/nodes?ids=...` | Fetch only the nodes you need to reduce payload | | Export images | `GET /v1/images/:key?ids=...&format=svg` | Renders nodes as SVG/PNG/PDF; URLs expire in 14 days | | Get styles | `GET /v1/files/:key/styles` | Lists all published color, text, and effect styles | | Get components | `GET /v1/files/:key/components` | Lists all published components with metadata | | Get component sets | `GET /v1/files/:key/component_sets` | Returns variant groupings for components | | Get variables | `GET /v1/files/:key/variables/local` | Extracts Figma Variables (colors, spacing, etc.) | | Publish variables | `POST /v1/variables` | Publishes local variables organization-wide | | Token extraction | Parse styles from file response, transform to CSS/JSON | No built-in "extract tokens" endpoint exists | | CI sync | GitHub Actions cron + `peter-evans/create-pull-request` | Auto-sync PRs on Figma file changes | ## Figma File Organization | Section | Contents | | ---------- | --------------------------------------------------- | | Colors | All color styles with `/` hierarchy (`Primary/500`) | | Typography | Text styles (`Heading/Large`, `Body/Regular`) | | Spacing | Spacing guide values | | Components | Variant groups (`Button/Primary`, `Card/Default`) | | Icons | All icons in one exportable frame | ## Common Mistakes | Mistake | Fix | | --------------------------------------------------------- | ---------------------------------------------------------------- | | Using fabricated API methods like `extractDesignTokens()` | Parse styles from `GET /v1/files/:key` response manually | | Hardcoding Figma values instead of using tokens | Extract tokens to CSS variables, reference with `var()` | | Not normalizing Figma style names | Lowercase + replace special chars with hyphens | | Forgetting Figma uses 0-1 RGB not 0-255 | Multiply by 255 and round before hex conversion | | No API response caching | Cache with TTL to avoid rate limits | | Manual icon exports | Automate with `GET /v1/images/:key` + React component generation | | No CI sync workflow | GitHub Actions cron + `create-pull-request` action | | Using expired image URLs | Image export URLs expire in 14 days; re-fetch before use | ## Libraries | Package | Purpose | | ---------------------- | ---------------------------------------- | | `figma-api` | Community Figma REST API client (typed) | | `@figma/rest-api-spec` | Official TypeScript types for Figma API | | `style-dictionary` | Transform design tokens across platforms | | `svgo` | Optimize exported SVGs before use | | `@svgr/core` | Convert SVG files to React components | ## Delegation - **Design systems**: see `design-system` skill - **Asset optimization**: see `asset-manager` skill ## References - [Setup and Authentication](references/setup.md) - [Design Tokens](references/design-tokens.md) - [Asset Export](references/asset-export.md) - [Component Generation](references/component-generation.md) - [CI Automation](references/ci-automation.md) - [Troubleshooting](references/troubleshooting.md)
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.