Figma shipped generative plugins. Your system decides if they're useful
Figma stopped treating plugins as developer-only this week. You can now prompt an agent to build them.
That's a shift for solo founders. I've been writing that your Figma file just became an agent's workspace — now the file also builds the tools that run inside it. You don't open an IDE to add power to your canvas. You describe it.
Generative plugins and shaders are useful only if your system is tight enough to constrain them: they amplify what you already defined and drift the moment you ask them to decide.
What did Figma actually ship on September 1?
Figma shipped prompt-to-build for two things that required code.
First, generative plugins. Tell the Figma agent what you want — "reorder layers," "apply spacing," "find and replace colors" — and it writes a plugin with native controls. No local setup. It lives in your file and works across files.
Second, shaders. GPU programs that bend pixels as fills or effects, now composable and animatable. Stack them, keyframe with Motion, or make them react to hover. At Config they were prompt-to-effect; now they're publishable.
Per the Figma release notes for generative plugins and shaders, you can now publish to Community or privately to your org, view and download the code, and edit via the MCP server. The quick start guide to generative plugins and shaders shows the flow, and the behind-the-build story for generative plugins and shaders notes that copying a frame with shaders into an external agent now renders correctly in React.
Why do generative plugins change the solo founder's workflow?
They move custom tooling from "someday" to "this afternoon."
Solo builders always needed small tools — a sorter for messy auto layout, a checker for off-system colors. Building a real plugin took a day you didn't have. Now you describe it in a sentence and test it in minutes.
The file isn't a picture you export. It's where agents read your system. Generative plugins extend that: the file also builds the helpers that keep it honest. A locked spacing scale means you can spin up a checker on Tuesday and catch drift before Friday.
You'll build more than you can maintain. Twelve half-working plugins are worse than two you trust. The win is that "I wish Figma did this" now fits inside one session.
How do you stop generated tools from creating drift?
You give the agent less freedom, not more.
Ask loosely and you'll get 12 button variants and a shadow that breaks the system. The fix is constraints before prompting.
Lock the set first. I use six buttons, cards at 10px radius, controls at 6px, 8px base, one type pairing. Put that in a file the agent reads — a Figma skill, a CLAUDE.md, or a Cursor rule — so it can't invent. Name rules as facts, not adjectives.
Review the code, not just the preview. Did it use your spacing variable or hard-code 17px? Did it call your component or make a new frame? Skip that and you ship drift.
Export and confirm. Copy a frame with the shader into Claude Code or Cursor via the MCP server and confirm it renders in React. Figma's team built for this — use it as the test. If React doesn't match the canvas, the tool isn't done.
When should you prompt versus build by hand?
Prompt when the job is clear and repeatable. Build by hand when it encodes taste.
Prompt for sorting, spacing fixes, token swaps, and checks like "flag layers not using auto layout." These are plumbing where the answer is right or wrong. With good rules, the agent nails them in one pass.
Don't prompt for what defines the brand. A shader that sets texture, a plugin that picks colors, a helper that decides hierarchy — those aren't helpers, they're authors. Let a tool author those and you'll get the median of the internet with your name on it. I keep a short hand-build window each week for that work.
If you can write what good looks like in one sentence, prompt it. If you can't, sketch by hand first. You'll judge faster when you know the bar.
Generative plugins don't remove the gate. They give you more to run through it.
Frequently asked questions
Figma shipped prompt-to-build for generative plugins and shaders through the Figma agent. You describe the tool or effect, the agent writes the code, and you get native plugins with on-canvas controls plus shaders that support animation and interactivity. As of September 1, you can publish them to Community or privately to your org, view the code, and edit them via the Figma MCP server.
About the author
mosh
mosh is a product designer for growth, working with design thinking and ever-improving design systems. What matters: fixing conversion, whether in B2B dashboards or direct-consumer apps.
Keep reading
- SaaS activity tracking: designing an admin log teams trust
Admins needed to see every team action in one place. Research with two managers and eight user stories turned a confusing log into filters, search, share, and export.
- GymProLuxe: turning a resistance kit into a training system
GymProLuxe sold trusted hardware but motivation faded after delivery. Premium app UX gave every owner a daily plan matched to their kit.
- ScoreAi: match search redesign that lifted engagement
ScoreAi had demand but its match search leaked engagement. A conversion-first rebuild of hierarchy, scanning, and onboarding fixed discovery.