anomalyco/opencode/figma-use
Claude Code and agent skill by anomalyco/opencode
- community
Checking that the SKILL.md file is still in the repository.
**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
npx vskill@latest install anomalyco/opencode/figma-useSKILL.md
The same SKILL.md was published earlier as anomalyco/opencode/figma-use.
use_figma — Figma Plugin API Skill
Use the use_figma 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 `use_figma`. 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 usage — 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:use_figma,get_screenshot,get_metadata,create_new_file". One round trip beats six.
If the task involves building or updating a full page, screen, or multi-section layout in Figma from code, also load figma-generate-design. It provides the workflow for discovering design system components via search_design_system, importing them, and assembling screens incrementally. Both skills work together: this one for the API rules, that one for the screen-building workflow.
If the task involves creating or building a component in Figma (even a single component), also load figma-generate-library. It provides the component creation workflow — variable foundations, variant sets, design token bindings — that figma-use alone doesn't cover.
Before anything, load plugin-api-standalone.index.md to understand what is possible. When you are asked to write plugin API code, use this context to grep plugin-api-standalone.d.ts for relevant types, methods, and properties. This is the definitive source of truth for the API surface. It is a large typings file, so do not load it all at once, grep for relevant sections as needed.
IMPORTANT: Whenever you work with design systems, start with working-with-design-systems/wwds.md to understand the key concepts, processes, and guidelines for working with design systems in Figma. Then load the more specific references for components, variables, text styles, and effect styles as needed.
1. Critical Rules
- Use `return` to send data back. The return value is JSON-serialized automatically (objects, arrays, strings, numbers). Do NOT call
figma.closePlugin()or wrap code in an async IIFE — this is handled for you. - Write plain JavaScript with top-level `await` and `return`. Code is automatically wrapped in an async context. Do NOT wrap in
(async () => { ... })(). -
figma.notify()throws "not implemented" — never use it
3a. Return node IDs and keep workflow state outside the Figma file. Set human-readable component purpose and usage in node.description only on a COMPONENT or COMPONENT_SET — never on a frame or instance. 3b. Narrow before accessing type-specific properties. Check node.type, use a capability guard such as "characters" in node, or prefilter with findAllWithCriteria. characters requires a text-capable node; optional chaining does not protect unsupported property access.
-
console.log()is NOT returned — usereturnfor output - Size construction calls for safe retry and validate from evidence. Do not split a working operation solely to create validation checkpoints. Batch related work when the resulting script remains safe to retry; a complete section or page may be built in one call. Split when crossing page context, when partial execution would be difficult to recover, or after an actual failure requires a targeted retry. Return affected IDs and relevant counts, names, or bounds from each write—this counts as structural validation. Run a separate structural check only when required evidence is missing or after a relevant mutation. Normally take one screenshot after composition and one after a visual fix. The most recent passing screenshot is the final check; do not repeat it when nothing relevant changed. Stop once requirements pass.
- Colors are 0–1 range (not 0–255):
{r: 1, g: 0, b: 0}= red. Paintcolorobjects use{r, g, b}only — no `a` field; opacity goes at the paint level ({ type: 'SOLID', color: {...}, opacity: 0.5 }). - Fills/strokes are read-only arrays — clone, modify, reassign
- Every text edit follows the canonical recipe: load font → `await` → mutate → return affected node IDs. Skipping the load throws
Cannot write to node with unloaded font "<family> <style>". The rule covers more thancharacters— it applies to any operation on nodes with unloaded fonts (appendChild,insertChild,setBoundVariable,setExplicitVariableModeForCollection,setValueForMode,findAllcallbacks touching text). When mutating existing text, load the node's current fonts viagetStyledTextSegments(['fontName']), not a hardcoded default. Inter is preloaded in most environments so other families surface this bug more often — the recipe is the same for every font. Useawait figma.listAvailableFontsAsync()first if the style string is unverified — never guess ("SemiBold"vs"Semi Bold"is a common footgun). ForFONT_FAMILY-scoped variables, load every value across every relevant mode beforesetBoundVariable("fontFamily", …),setValueForMode, orsetExplicitVariableModeForCollection.lineHeight/letterSpacingtake{unit, value}, not bare numbers. See Canonical text-edit recipe. - Pages load incrementally — use
await figma.setCurrentPageAsync(page)to switch pages and load their content. The sync setterfigma.currentPage = pagedoes NOT work and throws"Setting figma.currentPage is not supported". Page context resets to the first page at the start of everyuse_figmacall, so re-switch each call; switch at most once per call and fan multi-page work out in parallel — see Page Rules and gotchas.md. setBoundVariableForPaintreturns a NEW paint — must capture and reassigncreateVariableaccepts collection object or ID string (object preferred)- `layoutSizingHorizontal/Vertical` is value-restricted by structural context — `FIXED` always works, `HUG` and `FILL` do not.
'HUG'is valid only on an auto-layout frame itself OR on a TEXT child of one.'FILL'is valid only on a child of an auto-layout frame that is also not absolute-positioned, not inside an immutable frame, and not a canvas-grid child. Practical consequence: append to an auto-layout parent FIRST, then setHUG/FILL— a newly-created or unparented node can't satisfy the rule yet. The property itself exists on everySceneNode; the error is value-rejection, not "no such property". See Gotchas.
12a. Use auto-layout for containers that hold related children. When children have a structural relationship — stacked, side-by-side, aligned, gapped, hugged — wrap them in figma.createAutoLayout(), not figma.createFrame() with absolute x/y. Absolute coordinates govern where a container sits on the canvas; auto-layout governs how its children relate inside it. Skipping the container leaves no protection against text reflow, content changes, or overlap. 12b. `layoutSizing*` and `*AxisSizingMode` are different enums — don't cross them. layoutSizingHorizontal/layoutSizingVertical (set on a child) take 'FIXED'|'HUG'|'FILL'; primaryAxisSizingMode/counterAxisSizingMode (set on the frame itself) take 'FIXED'|'AUTO'. So layoutSizingVertical = 'AUTO' is invalid (use 'HUG'), and counterAxisSizingMode = 'FILL' throws Expected 'FIXED' | 'AUTO', received 'FILL' (use 'FIXED'/'AUTO'). Two more errors from the same setter — Error: in set_layoutSizingHorizontal: node must be an auto-layout frame or a child of an auto-layout frame and Error: in set_layoutSizingHorizontal: FILL can only be set on children of auto-layout frames — mean the node isn't in an auto-layout context yet; recommendation: make the parent auto-layout (`figma.createAutoLayout()`) and `appendChild` the node before setting (see Rule 12). See Gotchas. 12c. `resize()` resets sizing modes to `FIXED`, so call it BEFORE setting `layoutSizing*`. A wrapping TEXT block needs textAutoResize = 'HEIGHT' plus an explicit FIXED width (resize()), NOT FILL alone — the default WIDTH_AND_HEIGHT mode ignores FILL and collapses the node to a near-zero-width thread. Verify node.width > 0 afterward.
- Position new top-level nodes away from (0,0). Nodes appended directly to the page default to (0,0). Scan
figma.currentPage.childrento find a clear position (e.g., to the right of the rightmost node). This only applies to page-level nodes — nodes nested inside other frames or auto-layout containers are positioned by their parent. See Gotchas. - On `use_figma` error, obey `safeToRetryWithoutCanvasRead`. If
true, fix the error and retry. Iffalse, read the canvas, determine what changed, then make changes. See Error Recovery. - MUST `return` ALL created/mutated node IDs. Whenever a script creates new nodes or mutates existing ones on the canvas, collect every affected node ID and return them in a structured object (e.g.
return { createdNodeIds: [...], mutatedNodeIds: [...] }). This is essential for subsequent calls to reference, validate, or clean up those nodes. No state persists acrossuse_figmacalls, so pass IDs from previous calls as string literals, not variables. See common-patterns.md for worked multi-step examples. - Always set `variable.scopes` explicitly when creating variables. The default
ALL_SCOPESpollutes every property picker — almost never what you want. Use specific scopes like["FRAME_FILL", "SHAPE_FILL"]for backgrounds,["TEXT_FILL"]for text colors,["GAP"]for spacing, etc. See variable-patterns.md for the full list. - `await` every Promise. Never leave a Promise unawaited — unawaited async calls (e.g.
figma.loadFontAsync(...)withoutawait, orfigma.setCurrentPageAsync(page)withoutawait) will fire-and-forget, causing silent failures or race conditions. The script may return before the async operation completes, leading to missing data or half-applied changes. - Never read `componentPropertyDefinitions` from a variant component. Narrow the owner first: use the node itself when it is a
COMPONENT_SET, use aCOMPONENTonly when its parent is not aCOMPONENT_SET, and otherwise promote a variantCOMPONENTto its parent set. Optional chaining does not make the getter safe. See Component-property owner narrowing.
For detailed WRONG/CORRECT examples of each rule, see Gotchas & Common Mistakes.
2. Page Rules (Critical)
The async-only setter and the per-call context reset are covered in Rule 9. This section elaborates the one rule that needs a worked example: switch pages at most once per script, and fan multi-page work out in parallel.
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingpackages/plugins/figma/skills/figma-use/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/anomalyco/opencode/figma-use)