figma-use

Automates JavaScript-driven inspection and manipulation of Figma files via Plugin API workflows.

12|7|Updated Sep 15, 2025
One-click install
npx skills add https://github.com/allofmeng/streamline_project --skill figma-use-allofmeng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: figma-use
Source: https://github.com/allofmeng/streamline_project/tree/main/.agents/skills/figma-use
Command: npx skills add https://github.com/allofmeng/streamline_project --skill figma-use-allofmeng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates safe, repeatable Figma file manipulation by providing a structured use_figma workflow to run JavaScript in the Figma file context, enabling read/write operations, component workflows, and design-system patterns.

Core Features & Use Cases

  • Build and modify components, frames, text, and assets via scripted actions
  • Manage design-system patterns such as variables, text styles, and component properties
  • Validate changes with metadata checks and incremental steps, with built-in error-recovery guidance
  • Integrate with plugin APIs to switch pages, load fonts, and return structured results for downstream tooling

Quick Start

Run a tiny use_figma script to inspect the current page and return basic metadata.

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 file manipulation across multiple pages?

You can automate Figma file manipulation by running JavaScript scripts in the file context to read, write, and inspect design assets across multiple pages using the Plugin API.

Can I manage design-system patterns like variables and text styles via scripts?

Yes, you can manage design-system patterns by scripting actions to modify variables, text styles, and component properties directly within the Figma file.

How do I load fonts before editing text in Figma automation workflows?

Loading fonts is required before executing text edits in Figma automation workflows, ensuring the asynchronous page switching and promise handling return structured data successfully.

Does this approach support incremental workflows with error recovery?

Yes, the approach supports incremental workflows by validating changes with metadata checks and providing built-in error-recovery guidelines to handle promise rejections.

What is the best way to extract metadata from Figma components?

The best way to extract metadata from Figma components is by running a script to inspect the current page, read asset properties, and return structured results for downstream tooling.

Can I switch pages asynchronously during Figma design automation?

Yes, you can switch pages asynchronously during Figma design automation by using setCurrentPageAsync, which handles promise resolution before executing subsequent manipulation steps.