Figma no longer just designs: now it builds your own tools (and this changes how we operate as an agency)

All of this runs on "skills": reusable instructions that package your team's workflow and conventions, so the agent doesn't invent its own style every time you use it.

Why this isn't just "another AI feature"

The difference from previous AI updates in Figma is that this one democratizes the building of internal tools. Before, if a design team wanted a specific plugin —say, one that reorders layers by contrast criteria, or generates component variants with custom business rules— they needed someone who knew JavaScript and Figma's plugin API. Now that plugin gets described in natural language and appears in the file.

This connects with something we already saw coming: the line between "designer" and "developer" keeps blurring, not because designers learn to code, but because the agent absorbs that friction. Dylan Field, Figma's CEO, said it in the launch blog: AI lowered the entry floor, but the ceiling is still raised by people brave enough to build with these new tools.

The risk nobody's mentioning

Here's the angle that matters to us as an agency and almost nobody is covering: generative plugins without governance are shadow tools on steroids. If anyone on the team can create their own tool inside a shared file, in a few months you'll have fifteen variants of "the plugin that orders layers" made by different people, with different criteria, no documentation, and no real version control.

It's not hypothetical. We already lived it with the uncontrolled growth of component libraries and duplicated styles when Figma opened Auto Layout and variables to everyone without a clear governance layer. The lesson from that phase was simple: the speed the individual team gains is lost in system consistency if nobody audits what's being created.

The same applies to code layers. A design layer converting to interactive code with a click sounds wonderful until that code lands in production without review, or until two people "extract to design" the same component and generate diverging versions.

What this means for agencies and product teams

If you run a design team or an agency like ours, here's what would change in how you operate over the next few months:

- Define who can publish generative plugins before people start creating them. Figma already announced that soon you'll be able to publish at team, organization, or community level — that needs an owner and a review process, just like any internal library.

- Treat the agent's "skills" as living documentation of your design system, not as an extra. If your team already has naming, spacing, or accessibility conventions, package them now as skills before everyone improvises their own.

- Leverage MCP connectors to close the design-development-business loop. If a component can directly reference a GitHub ticket or a Notion brief, there's a real opportunity to cut handoff time — but only if your stack is already organized (if your tickets are poorly written, the agent will inherit that mess).

- Don't confuse "faster to prototype" with "ready for production". Code layers are excellent for exploring directions in parallel, but they need the same code review process as any other pull request before touching production.

At Geek Vibes we've already started mapping which parts of our workflow with clients benefit from this —mainly quick variant exploration and spec generation for developers— and which need an explicit human review layer before the agent gets permission to write directly to our repos.

The real point

Figma isn't selling "AI that designs for you". It's selling the possibility for every team to build its own tools without relying on an internal plugin engineer. That's real power, but power without governance becomes design tech debt. The question we ask the teams we work with isn't "have you tried generative plugins yet?" but "who audits what gets built with them?".

If you're evaluating how to integrate these tools into your design-development workflow without losing consistency, at Geek Vibes we help agencies and product teams build that governance layer before speed becomes chaos. Write us at comercial@geekvibes.agency.