Your design team does the same thing by hand a hundred times. Renaming layers, pasting real data, checking tokens. A plugin does it once, correctly.
Your design team is doing something by hand a hundred times a week. Renaming layers to match a convention. Pasting real customer data into mockups one field at a time. Checking that every component still uses a token and not a hardcoded hex. Exporting assets and reorganising them into the folder structure engineering expects.
None of that is design work. All of it is a plugin.
What I build
Real data in your designs. Connect Figma to your API, CMS, or database so a mockup fills with actual product names, prices, and copy instead of lorem ipsum. Designs stop lying about how the interface behaves when a name is 60 characters long.
Design system enforcement. Scan a file and report every detached component, hardcoded colour, and off-scale spacing value. Catch drift before it reaches a developer.
Bulk operations. Rename, restructure, retag, and export across hundreds of layers to your own rules, in one pass.
Handoff automation. Push tokens, specs, or assets out of Figma and into the format your engineering team actually consumes.
Where I stand on Figma specifically
Straight answer: I'm building my first Figma plugin now. I've shipped plugins on other platforms, including one accepted into a public marketplace after independent review, and I work in Figma and Pencil daily on real client design work. The Figma Plugin API is a TypeScript surface over a scene graph, which is familiar territory.
If you'd rather hire someone with five shipped Figma plugins behind them, that's a fair call and I'd respect it. I'd rather you knew that before you paid me than found out in week three. What I can tell you is that the hard part of this work is rarely the Figma API, it's understanding the workflow you're trying to remove, and that part I've done many times.
How it works
- A call. You show me the repetitive thing. Free, 30 minutes.
- Scope. What it does, what it doesn't, what it costs. In writing, before you commit.
- Build. Something you can run in your file by around week two.
- Handover. Source, docs, and a build you can publish to the community or keep private to your organisation.
What you get
The code is yours, documented well enough that another developer can maintain it without me.
Ready to start?
Tell me what your designers keep doing by hand. If a plugin isn't the answer, or one in the community already does it, I'll say so on the call and charge you nothing.
Reach me by email, on LinkedIn, or fill in the form on this page.