Figma Use
Run Figma Plugin API scripts for canvas edits, inspections, variables, and design-system work before or alongside UI implementation.
Overview
figma-use is an agent skill for the Build phase that runs Figma Plugin API scripts for canvas, inspection, variables, and design-system tasks and gates other Figma skills in the catalogue.
Install
npx skills add https://github.com/nexu-io/open-design --skill figma-useWhat is this skill?
- Prerequisite entry for every other Figma skill in the Open Design catalogue
- Figma Plugin API scripts for canvas writes, inspections, and variables
- Design-system mode aligned with upstream figma/skills bundle
- Trigger phrases: figma use, figma plugin api, figma canvas, figma scripts
- Catalogue discovery plus install path to full upstream assets and references
- Prerequisite for every other Figma skill in this catalogue
Adoption & trust: 790 installs on skills.sh; 61.4k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need repeatable Figma canvas and design-system changes from your agent but only have a thin catalogue pointer without the full Plugin API workflow installed.
Who is it for?
Solo builders shipping web or mobile UI who automate Figma alongside Claude Code, Cursor, or Codex and plan to use multiple Figma skills from Open Design.
Skip if: Teams that do not use Figma, builders who only need static mock review with no Plugin API automation, or anyone expecting a self-contained runtime without installing upstream figma/skills.
When should I use this skill?
User mentions figma use, figma plugin api, figma canvas, or figma scripts, or needs canvas writes, inspections, variables, or design-system work in Figma.
What do I get? / Deliverables
Your agent discovers figma-use by trigger, installs the upstream figma/skills bundle, and can invoke Plugin API scripts before other Figma catalogue skills.
- Installed upstream Figma skills bundle
- Agent-invoked Plugin API script runs on the Figma canvas
- Design-system and variable updates driven from the agent
Recommended Skills
Journey fit
Figma canvas and design-system automation sits in the Build phase where solo builders shape product UI and shared components. Frontend subphase is the canonical shelf for design-to-code and component-library work driven from Figma.
How it compares
A catalogue and prerequisite integration skill for Figma’s upstream skill bundle—not a standalone MCP server or a generic screenshot-to-code converter.
Common Questions / FAQ
Who is figma-use for?
Solo and indie builders who design in Figma and want their coding agent to run Plugin API scripts for canvas, variables, and design-system work.
When should I use figma-use?
During Build (frontend) when you are syncing components, inspecting the canvas, or scripting design tokens; install it before any other Figma skill in the Open Design catalogue.
Is figma-use safe to install?
Review the Security Audits panel on this Prism page and inspect the upstream https://github.com/figma/skills repo before granting filesystem or network access to your agent.
SKILL.md
READMESKILL.md - Figma Use
# figma-use > Curated from Figma's MCP server guide. ## What it does Run Figma Plugin API scripts for canvas writes, inspections, variables, and design-system work. Prerequisite for every other Figma skill in this catalogue. ## Source - Upstream: https://github.com/figma/skills - Category: `figma` ## How to use This catalogue entry advertises the skill in Open Design so the agent discovers it during planning. To run the full upstream workflow with its original assets, scripts, and references, install the upstream bundle into your active agent's skills directory: ```bash # Inspect the upstream README for exact paths open https://github.com/figma/skills ``` Then ask the agent to invoke this skill by name (`figma-use`) or with one of the trigger phrases listed in this skill's frontmatter.