figma-use

Name: figma-use
Author: openai

24kstars1.6kforks

How to install figma-use?

openai/skills/figma-use

$npx -y skills add openai/skills --skill figma-use

Installs into the current project.

Summary

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 r

Files · 1

View on GitHub

SKILL.md

1	# use_figma — Figma Plugin API Skill
2
3	Use `use_figma` MCP to execute JavaScript in Figma files via the Plugin API. All detailed reference docs live in `references/`.
4
5	Always pass `skillNames: "figma-use"` when calling `use_figma`. This is a logging parameter used to track skill usage — it does not affect execution.
6
7	If the task involves building or updating a full page, screen, or multi-section layout in Figma from code, also load [figma-generate-design](../figma-generate-design/SKILL.md). 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.
8
9	Before anything, load [plugin-api-standalone.index.md](references/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](references/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.
10
11	IMPORTANT: Whenever you work with design systems, start with [working-with-design-systems/wwds.md](references/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.
12
13	## 1. Critical Rules
14
15	1. 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.
16	2. Write plain JavaScript with top-level `await` and `return`. Code is automatically wrapped in an async context. Do NOT wrap in `(async () => { ... })()`.
17	3. `figma.notify()` throws "not implemented" — never use it
18	3a. `getPluginData()` / `setPluginData()` are not supported in `use_figma` — do not use them. Use `getSharedPluginData()` / `setSharedPluginData()` instead (these ARE supported), or track node IDs by returning them and passing them to subsequent calls.
19	4. `console.log()` is NOT returned — use `return` for output
20	5. Work incrementally in small steps. Break large operations into multiple `use_figma` calls. Validate after each step. This is the single most important practice for avoiding bugs.
21	6. Colors are 0–1 range (not 0–255): `{r: 1, g: 0, b: 0}` = red
22	7. Fills/strokes are read-only arrays — clone, modify, reassign
23	8. Font MUST be loaded before any text operation: `await figma.loadFontAsync({family, style})`
24	9. Pages load incrementally — use `await figma.setCurrentPageAsync(page)` to switch pages and load their content (see Page Rules below)
25	10. `setBoundVariableForPaint` returns a NEW paint — must capture and reassign
26	11. `createVariable` accepts collection object or ID string (object preferred)
27	12. `layoutSizingHorizontal/Vertical = 'FILL'` MUST be set AFTER `parent.appendChild(child)` — setting before append throws. Same applies to `'HUG'` on non-auto-layout nodes.
28	13. Position new top-level nodes away from (0,0). Nodes appended directly to the page default to (0,0). Scan `figma.currentPage.children` to 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](references/gotchas.md).
29	14. On `use_figma` error, STOP. Do NOT immediately retry. Failed scripts are atomic — if a script errors, it is not executed at all and no changes are made to the file. Read the error message carefully, fix the script, then retry. See [Error Recovery](#6-error-recovery--self-correction).
30	15. 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.
31	16. Always set `variable.scopes` explicitly when creating variables. The default `ALL_SCOPES` pollutes ever

People who liked this also viewed

6 picks

Type

figma-use

24kstars1.6kforks

View on GitHub

How to install figma-use?

openai/skills/figma-use

$npx -y skills add openai/skills --skill figma-use

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# use_figma — Figma Plugin API Skill
2
3	Use `use_figma` MCP to execute JavaScript in Figma files via the Plugin API. All detailed reference docs live in `references/`.
4
5	Always pass `skillNames: "figma-use"` when calling `use_figma`. This is a logging parameter used to track skill usage — it does not affect execution.
6
7	If the task involves building or updating a full page, screen, or multi-section layout in Figma from code, also load [figma-generate-design](../figma-generate-design/SKILL.md). 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.
8
9	Before anything, load [plugin-api-standalone.index.md](references/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](references/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.
10
11	IMPORTANT: Whenever you work with design systems, start with [working-with-design-systems/wwds.md](references/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.
12
13	## 1. Critical Rules
14
15	1. 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.
16	2. Write plain JavaScript with top-level `await` and `return`. Code is automatically wrapped in an async context. Do NOT wrap in `(async () => { ... })()`.
17	3. `figma.notify()` throws "not implemented" — never use it
18	3a. `getPluginData()` / `setPluginData()` are not supported in `use_figma` — do not use them. Use `getSharedPluginData()` / `setSharedPluginData()` instead (these ARE supported), or track node IDs by returning them and passing them to subsequent calls.
19	4. `console.log()` is NOT returned — use `return` for output
20	5. Work incrementally in small steps. Break large operations into multiple `use_figma` calls. Validate after each step. This is the single most important practice for avoiding bugs.
21	6. Colors are 0–1 range (not 0–255): `{r: 1, g: 0, b: 0}` = red
22	7. Fills/strokes are read-only arrays — clone, modify, reassign
23	8. Font MUST be loaded before any text operation: `await figma.loadFontAsync({family, style})`
24	9. Pages load incrementally — use `await figma.setCurrentPageAsync(page)` to switch pages and load their content (see Page Rules below)
25	10. `setBoundVariableForPaint` returns a NEW paint — must capture and reassign
26	11. `createVariable` accepts collection object or ID string (object preferred)
27	12. `layoutSizingHorizontal/Vertical = 'FILL'` MUST be set AFTER `parent.appendChild(child)` — setting before append throws. Same applies to `'HUG'` on non-auto-layout nodes.
28	13. Position new top-level nodes away from (0,0). Nodes appended directly to the page default to (0,0). Scan `figma.currentPage.children` to 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](references/gotchas.md).
29	14. On `use_figma` error, STOP. Do NOT immediately retry. Failed scripts are atomic — if a script errors, it is not executed at all and no changes are made to the file. Read the error message carefully, fix the script, then retry. See [Error Recovery](#6-error-recovery--self-correction).
30	15. 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.
31	16. Always set `variable.scopes` explicitly when creating variables. The default `ALL_SCOPES` pollutes ever

People who liked this also viewed

6 picks

Type