figma-use
**MANDATORY prerequisite** — you MUST invoke this skill BEFORE every `use_figma` tool call. NEVER call `use_figma` directly without loading this skill first. Skipping it causes common, hard-to-debug failures. Trigger whenever the user wants to perform a write action or a unique read action that requires JavaScript execution in the Figma file context — e.g. create/edit/delete nodes, set up variables or tokens, build components and variants, modify auto-layout or fills, bind variables to properties, or inspect file structure programmatically.
Install
git clone https://github.com/figma/mcp-server-guide /tmp/mcp-server-guide && ln -s /tmp/mcp-server-guide/skills/figma-use ~/.claude/skills/figma-useFrom README
usefigma — Figma Plugin API Skill Use the usefigma tool to execute JavaScript in Figma files via the Plugin API. All detailed reference docs live in references/. Always include figma-use in the comma-separated skillNames parameter when calling usefigma. If this skill was loaded via an MCP resource, you MUST prefix the name with resource: (e.g. resource:figma-use). This is a logging parameter used to track skill — it does not affect execution. If Figma MCP tools appear as deferred tools, batch-load all their schemas in a single ToolSearch call using the select: syntax — e.g. ToolSearch query="select:usefigma,getscreenshot,getmetadata,createnewfile". One round trip beats six. MANDATORY for visible design changes: Before the first mutating usefigma call, load figma-generate-design alongside this skill and include both names in every mutating call’s skillNames.
More from this repo
figma-code-workflows
Import or upload local HTML or project files into Figma, choose editable Design frames, runnable Code Layers or...
figma-generative-plugins
**MANDATORY prerequisite** — load this skill before calling `create_generative_plugin` or `update_generative_plugin`.
figma-shaders
**MANDATORY prerequisite** — load this skill before calling `create_shader` or `update_shader`.