Figma plugins

What we build in Figma

Figma is where design decisions get made. A plugin is how those decisions leave Figma without being retyped somewhere else. We build plugins that read your file, act on it, and connect it to the systems your team already runs.

Typical work: sync variables to design tokens, generate components from data, run bulk edits across hundreds of layers, and turn handoff into a real pull request against your repo.

How it works

We build on the official Plugin API, with the UI, permissions and network access the job actually needs. If the plugin talks to a backend, we wire that in with proper auth.

The decision that shapes the build

Before anything is written, one question has to be settled: which side is the source of truth. If design owns the tokens, the tool reads the file and opens a pull request. If the codebase owns them, it flows the other way and the panel becomes a reader rather than a writer. Teams that skip this end up with a tool that fights itself, syncing in both directions with no rule for who wins.

The second question is smaller but just as practical: what format your codebase expects. CSS custom properties, a JSON token file, a framework-specific shape. The plugin has to write exactly that, so we agree it up front rather than guess.

When it is not worth building

If your team ships a handful of token changes a year, a person doing it by hand is cheaper than a tool, and we will tell you so. This pays off where the file changes weekly, where more than a few people touch it, or where the drift between design and production has already cost you a release.

What you get

A working plugin, the source code, and a short guide. If it belongs in the Figma Community we handle publishing; if it is internal, we package it for your organisation.