skills.rest
winetree94
winetree94COMMUNITY
Explore all skills by this author →
WebsiteGitHub

figma-use

Execute Figma Plugin API scripts with atomic steps and structured node ID returns.

Updated Aug 23, 2026
Search Tags:#automation#workflow#patterns#figma#plugin#design-systems#use_figma
One-click install
npx skills add https://github.com/winetree94/dotfiles --skill figma-use-winetree94
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: figma-use
Source: https://github.com/winetree94/dotfiles/tree/main/default/.agents/skills/figma-use
Command: npx skills add https://github.com/winetree94/dotfiles --skill figma-use-winetree94

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The use_figma skill provides a structured, frontmatter-driven approach to executing JavaScript in Figma files via the Plugin API, enabling safe, atomic steps and clear guidance to avoid common pitfalls.

Core Features & Use Cases

  • Atomic, rule-based execution: Write small, testable scripts that return structured data (e.g., createdNodeIds, mutatedNodeIds) for use in subsequent steps.
  • Incremental design-workflows: Validate file structure, pages, and component metadata across multiple calls, with explicit error-recovery guidance.
  • Rich references and patterns: Access plugin API patterns, design-system references, and best practices to build reliable Figma workflows.

Quick Start

Load the use_figma skill and start with a tiny, read-only query to confirm the environment and return a minimal data payload.

Frequently Asked Questions about figma-use

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Figma plugin workflows safely without breaking file data?▼

Safe Figma plugin scripting uses atomic, rule-based execution to apply incremental changes. This approach validates file structure across multiple pages and returns structured data like created or mutated node IDs for predictable, recoverable design workflows.

Why do my Figma plugin scripts fail when creating text nodes or switching pages?▼

Figma plugin scripts fail without explicit promise management. You must await asynchronous calls, load fonts before text operations, and switch pages using setCurrentPageAsync to ensure atomic execution and predictable results.

How do I read Figma file metadata and validate component structure across multiple pages?▼

You can read Figma file metadata and validate component structures by executing small, read-only plugin API scripts. These atomic queries inspect pages and components, returning minimal data payloads to confirm your environment before applying mutations.

What is the best way to track created and mutated nodes during Figma design automation?▼

Tracking Figma nodes requires scripts with strict return semantics. By enforcing atomic execution, your scripts must return all created or mutated node IDs as structured data, enabling safe validation and incremental design-system workflows.

Can I use Figma plugin API patterns to build reliable design-system workflows?▼

Yes, you can build reliable design-system workflows by applying structured plugin API patterns. This involves using frontmatter-driven scripts and best practice references to execute atomic steps, ensuring safe file mutations and clear error-recovery guidance.

Related Skills

Explore More Design & Creative Skills→
coinbasecoinbase
493

figma.audit-connect

Audit Figma Code Connect mapping files for accuracy and completeness.

Official
Advanced
elsolalelsolal
1

figma-use

Coordinate incremental use_figma calls to manipulate Figma documents via the plugin API.

Community
Advanced
LAF-USLAF-US

figma-use

Enforce preloading rules and atomic use_figma calls for the Figma Plugin API.

Official
Advanced
DevPelumiDevPelumi

figma-use

Enforce mandatory Figma Plugin API execution rules for use_figma tool calls.

Community
Advanced