figma-use CLI
A Figma CLI with read and write: shapes, text, components, variables and JSX from the command line. An unofficial route, Figma 126+ blocks debugging
- 609 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- An unofficial route, breakages on Figma updates are possible
- Edits your design files
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/figma-useDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- An unofficial route, breakages on Figma updates are possible
- Edits your design files
This is third-party code. Review the repository files before installing.
What it does
figma-use is a CLI that controls Figma from the terminal with commands or JSX: it creates shapes, text, icons and components, sets styles, layout and variables and exports images. By the author's description there are over a hundred commands. The README warns: Figma 126 and newer blocks remote debugging, so the tool works through `figma-use daemon start --pipe`. Installation: `npm install -g figma-use`, check with `npx figma-use status`. Version 0.13.5 from 03.07.2026, MIT license.
Who it is for. For developers and designers who need an agent with write access to Figma: it builds layouts, components and variables.
Good fit when
- You need an agent to create layouts and components in Figma
- You need to write variables and styles from the command line
- It is easier to describe a layout in JSX than in schemas
Not a fit when
- You need Figma's official route: the tool is unofficial
- You need a guarantee of working between Figma versions: breakages are possible
Example request
Create a frame with a grid of three cards in a copy of the Figma file and set their colors through variablesLimitations
The route is unofficial: Figma 126 and newer blocks remote debugging, the tool works through a daemon with the --pipe flag and breakages on Figma updates are possible. The CLI edits your design files, so access is broad: try it on a copy of the file.
How to disable. Remove the skill from the agent's folder or the plugin through the plugin manager.
FAQ
What can figma-use do?
Create and change Figma objects from the command line or JSX, work with styles and variables, export images.
Why is a daemon needed?
Figma 126 and newer blocks remote debugging, so it is launched through figma-use daemon start --pipe.
Is it safe for the file?
The tool edits the file, so try it on a copy.
Discussion
No questions or reviews yet.
Related
CLI toolsA free, two-way Figma MCP server: turns designs into framework-aware code and pushes code back to the canvas
Figma MCP Bridge
figma-mcp-bridge
A Figma Desktop plugin and an MCP server: an agent reads tokens, styles and components without the Figma REST API and its limits. Not from Figma
Figma Console MCP
figma-console-mcp
A two-way Figma MCP server for design systems: reads and writes variables, components and styles and syncs tokens with code
MCP bridge between an agent (Cursor, Claude Code, Codex) and Figma for reading designs and editing them on the canvas
Figma Community Resources
figma-community-resources
A list of open plugins, widgets, agent skills and developer resources for Figma shared on GitHub. A community repository, not endorsed by Figma
An MCP server that lets an agent read and edit Figma designs: colors, typography, components and export
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| figma-use (this entry) | no | 609 | ||
| Figma MCP Bridge | no | not required | 745 | reading Figma through a plugin without REST API limits |
| TemPad Dev | no | 593 | Figma layouts into JSX and Vue code with Tailwind |
README in short
The README describes a CLI for reading and writing in Figma with JSX and warns about the debugging block in Figma 126+. MIT license.