Generate plugins with the Figma agent

Extend what's possible in your design files by building custom plugins through prompting the Figma agent. No need to understand code or technical terminology—you explain it, the Figma agent will build it.

What are generative plugins?

Plugins are applications that extend the functionality of Figma’s products using Figma’s Plugin API. Generative plugins are as their name suggests—they are built by prompting the Figma agent and the agent writes the code for you so that you don’t have to. You can even build plugins for Figma Draw and Motion.

Types of generative plugins in Figma

There are three types of generative plugins that the Figma agent can help you build:

Explore plugins built by Figma

The Figma team has built dozens of plugins—like chart generators and ASCII art transformers—for everyone use in their design files. To browse Figma's full plugin offering:

1. Open the Tools tab from your design file and filter the source by From Figma. 
2. Click the Filter icon and select Plugins.

Plugins built by Figma are free to use.

Learn about how to use a specific plugin built by Figma.

Make your own plugin

Step 1: Prompt the agent

To build your own plugin using the Figma agent:

1. Open a Figma Design file.
2. Click Agents in the navigation bar to open the Figma agent and start a new chat.
3. In the prompt box, type Build me a plugin and describe what you want the plugin to do. If you’re not sure where to start, try out one of the prompts below to start!
4. Test your plugin, and iterate with the agent as needed.

Try these prompts

 
 Density mode switcher: Build a plugin that takes my selected frames and produces compact, default, and spacious versions—scaling spacing tokens proportionally so I can present three density options to stakeholders without duplicating the work manually.

Layer hygiene linter: Build a plugin that audits all layers in my file for unnamed layers, hidden orphan layers, empty groups, redundant nesting, near-duplicate components, and file complexity. Before scanning, let me choose which categories and which pages to audit. Show results as collapsible sections with an Ignore button per row, and let me return to settings to re-configure and re-scan.

Accessibility checks: Build a plugin that audits designs for WCAG contrast failures (with AA/AAA toggle, selection vs. page scope, and a show-only mode) and suggests fixes from the file's local color variables. Each failing layer should show two fix options—one for the text fill and one for the background fill — each with a color swatch preview, a Fix button, and a "Browse variables…" fallback picker if no compliant variable exists. After the first audit, re-audit automatically in real time whenever a fill changes.

Note: The Figma agent is building you a fully coded plugin and may take a few moments to finish.

Basic tips for prompting

Whether you are a seasoned builder or you're writing your very first prompt, getting a great plugin usually comes down to describing what you want to the Figma agent.

• Be explicit that you want to "build a plugin."
• Describe what you want to see. You don't need to know how plugins work or any technical terminology—just describe what you want to see.

Get even more prompting tips.

Step 2: Test your plugin

Testing and iteration is a crucial part of any building process to make sure your resource works as intended. Test your plugin in a variety of scenarios to confirm it works properly and is free of bugs and crashes.

Tip: View the code behind your generated plugin to how it works, or use it to troubleshoot issues or changes you’re trying to make. Learn how to view the code for your plugin.

Step 3: Iterate

The path to building something is iterative and almost always requires refinement. You don’t have to get it right in one prompt. A brief, high-level prompt that explains the general behavior that you want is an effective way to begin. After that, you can move into refining the details and controls.

A few iterating tips:

• If you already know there are multiple changes you want to make, consider bundling them in one message to save time.
• Make sure to test as you go. Test the tool on a variety of inputs early and often. Make sure to use a duplicate of the design to test your plugin on.
• When to start fresh: If after a few prompts you’re not getting closer to what you envisioned, you can take your learnings and start fresh with more specificity.

Share your plugin

If you’d like to share your generative plugin with others, there are a few ways to do this:

• Publish the generative plugin to the Figma Community for others to discover and use
• Publish the internal generative plugins that are private to your organization

Before you share your plugin, make sure to thoroughly test it and ensure that it works properly in a variety of environments and situations.

Continue your learning journey

Playground file

Want more hands on practice with generative plugins? Grab a copy of the Config 2026 playground file and check out the Generative plugins and shaders page.

Help center articles

For more information on generative plugins, check out:

• Manage generative plugins as a creator
• Prompting tips for generative plugins and shaders
• About building plugins
• Use plugins in files

FAQ

What is the difference between generative plugins and classic plugins?

There are a few differences between generative plugins and classic plugins such as environment in which their built, third-party API support, and UI customization. Using the agent to build plugins is a great option if you don’t want to write the code yourself, while the classic way of building plugins is great if you want more control over the code.

To learn more, check out the article About building plugins in Figma.

What does this mean for creators of classic plugins?

You do not need to change the way you build or host plugins today. We don’t expect the introduction of generative plugins to change the usage of your plugins.

We’re continuing to invest in APIs and developer resources for partners and individuals who want to build plugins in their individual development environment and host plugins locally.

If you would like to migrate your plugin to be hosted by Figma and maintained through the agent, we will make this option available soon.

Do generative plugins cost AI credits?

Only when you are generating and editing plugins using the Figma agent will you be charged AI credits. It does not cost AI credits to run generative plugins.

Can I monetize plugins?

You can monetize classic plugins in the Community, but it’s not yet possible to monetize generative plugins.