figma-use

Run deterministic Figma plugin scripts to create, modify, and query canvas content.

3|Updated Mar 28, 2026

Search Tags:#automation #workflow #figma #metadata #error-recovery #plugin-api

Ready to run

npx skills add https://github.com/hulusi-tunc/unicorn-skills --skill figma-use-hulusi-tunc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: figma-use
Source: https://github.com/hulusi-tunc/unicorn-skills/tree/main/.claude/skills/figma-use
Command: npx skills add https://github.com/hulusi-tunc/unicorn-skills --skill figma-use-hulusi-tunc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates the safe execution and orchestration of Figma plugin code by providing a structured skill that loads context, runs atomic actions, and returns actionable outputs.

Core Features & Use Cases

Atomic, await'ed use_figma calls ensure deterministic behavior and safe error handling.
Structured returns (node IDs, counts, metadata) enable seamless chaining and validation across multiple steps.
Rich references and patterns guide font loading, variable usage, component workflows, and design-system workflows.

Quick Start

Use the use_figma skill to inspect the current file state and execute a small, safe script that creates a simple node and returns its ID

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 tasks deterministically without async errors?▼

To automate Figma plugin tasks deterministically, you must await async use_figma calls to ensure atomic execution and robust error handling. This method runs scripts that create, modify, and query canvas content while returning structured node IDs and metadata for reliable chaining.

What is the best way to build and validate Figma design systems programmatically?▼

Building and validating Figma design systems programmatically involves executing atomic plugin scripts that return structured metadata and node counts. This allows you to query components, styles, and variables iteratively while capturing actionable outputs for validation across multiple workflow steps.

Can I chain multiple Figma plugin scripts together safely?▼

You can chain multiple Figma plugin scripts together safely by using atomic, await'ed use_figma calls. These calls return structured outputs like node IDs, counts, and metadata, enabling seamless validation and reliable orchestration across multiple automated design steps.

How do I handle error recovery when running Figma automation workflows?▼

Handling error recovery in Figma automation workflows relies on executing atomic, await'ed plugin scripts. This deterministic approach ensures that if a script fails, the error is captured safely without corrupting the canvas, allowing structured metadata to guide subsequent recovery actions.

Does Figma automation support querying and loading specific design system references?▼

Figma automation supports querying and loading specific design system references. The skill provides rich patterns and references to guide font loading, variable usage, component workflows, and style management directly through deterministic plugin API scripts.

Why do my Figma plugin scripts return undefined or missing node IDs?▼

Figma plugin scripts return undefined or missing node IDs when async calls are not properly awaited. Using a deterministic skill that enforces atomic execution ensures scripts return structured IDs, counts, and metadata reliably after modifying canvas content.