Create Figma Plugin is an MIT-licensed TypeScript toolkit, published on npm as create-figma-plugin, that gives developers a documented and tested foundation for building plugins and widgets for Figma and FigJam.
What it is
Create Figma Plugin is a comprehensive toolkit for developing plugins and widgets for Figma, written in TypeScript and released under the MIT licence. It is distributed as the npm package create-figma-plugin and developed in the open on GitHub, where the repository has gathered 1,119 stars and 102 forks. The project spans both sides of the Figma platform: its topic list covers Figma plugins as well as FigJam plugins and FigJam widgets. Alongside the toolkit itself, the project maintains a documentation website at yuanqing.github.io/create-figma-plugin, organised into Introduction, Quick start, Configuration, UI, Utilities, Recipes, Reference plugins/widgets, Storybook and a Changelog.
The concrete problem it solves is the amount of undifferentiated setup that otherwise sits between a developer and a working plugin. Rather than assembling build configuration, a UI layer, shared helpers and example code by hand for every new plugin or widget, a developer starts from the toolkit's documented configuration and UI modules, its utilities and its recipes, and can read working code in the reference plugins and widgets. The repository also addresses the awkward part of the loop — testing toolkit changes against a plugin that already exists — by providing a script that symlinks a local checkout into an existing project so that project can be rebuilt against the local copy.
Key capabilities
- Covers both Figma plugins and FigJam artefacts: the topic list includes
figma-plugin, figma-plugins, figjam-plugin, figjam-plugins, figjam-widget and figjam-widgets.
- Ships a documented configuration layer, described on the documentation site under Configuration.
- Provides a UI layer for plugin interfaces, documented in its own UI section.
- Includes a Utilities module for shared plugin logic.
- Publishes a Recipes section together with Reference plugins/widgets that can be read as working examples.
- Includes a Storybook, documented as its own section of the documentation site.
- Provides
scripts/symlink.sh, which links a local checkout of the toolkit into an existing project (sh create-figma-plugin/scripts/symlink.sh create-figma-plugin my-project) so that the project's own npm run build picks up local changes.
Who uses it and how
- Developers building plugins and widgets for Figma and FigJam, who start from the Quick start and Configuration pages on the documentation site.
- Contributors to the toolkit itself, who work from a clone of the repository, install dependencies with
npm install, and build with npm run build using Node.js v22 and npm v11.
- Maintainers of existing plugins and widgets, who symlink a local copy of the toolkit into their project and rebuild it to verify a change.
- Contributors preparing a pull request, who work against the
next branch, where active development on the next release takes place, and who are expected to target that branch.
Getting started
The toolkit is consumed as the npm package create-figma-plugin, and the README directs users to the Quick start page on the documentation website rather than to the repository itself. To build the toolkit from source, clone the repository, run npm install, and then run npm run build with Node.js v22 and npm v11 installed.
How it compares
The facts provided do not name any comparable or competing tool, so Create Figma Plugin stands alone in this registry. It should be evaluated on its own documentation and reference implementations rather than against an alternative listed here.
When to use it — and when not to
Choose Create Figma Plugin when building a Figma plugin or FigJam widget and you want configuration and UI handled by a documented toolkit rather than assembled from scratch. A self-hoster needs only Node.js v22 and npm v11 to build it locally, since no database, storage or mail service is mentioned. Note that the README is addressed to contributors and is deliberately sparse, pointing users to an external documentation site, and that active development happens on the next branch — so anyone who wants a fully user-oriented entry point inside the repository itself, or who is not building for Figma or FigJam, should look elsewhere.
