figma-use

Execute Figma plugin scripts in headless mode to automate design tasks.

37|1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/terzigolu/warp-lite --skill figma-use-terzigolu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: figma-use
Source: https://github.com/terzigolu/warp-lite/tree/main/resources/bundled/mcp_skills/figma/figma-use
Command: npx skills add https://github.com/terzigolu/warp-lite --skill figma-use-terzigolu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Headless automation of Figma plugin scripts enables reliable, repeatable design tasks without opening the editor, reducing manual steps and enabling integration with automated workflows.

Core Features & Use Cases

  • Atomic script execution with deterministic outputs and no partial changes.
  • Page context management using setCurrentPageAsync and safe, structured returns to drive subsequent steps.
  • Comprehensive guidance for multi-step workflows, error recovery, and validation using get_metadata and get_screenshot.

Quick Start

Start by loading this skill and running a minimal use_figma script that creates a rectangle 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 scripts in headless mode?

Headless Figma plugin automation executes design tasks without opening the editor by running scripts atomically, managing page context with setCurrentPageAsync, and returning structured results to drive automated workflows.

What is the best way to run multi-step Figma workflows reliably?

Multi-step Figma workflows run reliably by executing atomic scripts with deterministic outputs, using setCurrentPageAsync for page context management, and safely returning structured data to drive subsequent steps without partial changes.

Can I validate headless Figma script execution results safely?

Headless Figma script validation uses get_metadata and get_screenshot to verify outputs, enforce error recovery, and ensure safe structured returns before proceeding to subsequent workflow steps.

Does headless Figma automation support atomic script execution?

Headless Figma automation supports atomic script execution, ensuring deterministic outputs and preventing partial changes by requiring every promise to be awaited and avoiding deprecated or unsafe plugin APIs.

Why should I avoid deprecated APIs in Figma plugin scripting?

Avoiding deprecated or unsafe APIs in Figma plugin scripting ensures safe headless execution, prevents workflow failures, and guarantees structured results are returned reliably without partial state changes.

What limitations exist when automating Figma design tasks headlessly?

Headless Figma automation requires awaiting every promise and returning data explicitly via return statements; it cannot use deprecated or unsafe APIs, and partial changes are prevented through atomic script execution.