The Philosophy of Purposeful Tooling

Building custom plugins in Figma is now accessible, but accessibility creates a risk of "plugin bloat." Before building, verify that the functionality doesn't already exist within Figma’s native agent capabilities or existing community plugins. The goal is to remove repetitive manual work, not to create a collection of redundant tools. Design leaders should centralize efforts: if multiple designers need the same tool, have one person build it, demo it, and maintain it to ensure consistency across the team.

A Formula for Effective Prompts

To ensure a plugin is useful and logical, structure your requests using a three-part formula:

  1. Trigger/Input: Define the scope (e.g., "When I select one or more frames...").
  2. Instructions: Provide specific, technical constraints (e.g., "Find every text layer, translate to French, keep layer structure intact").
  3. Output: Define the desired result (e.g., "Update the selected frames with the French text").

Avoid vague prompts like "make my designs better," which provide no actionable guidance to the AI and lead to unpredictable, low-quality results.

Real-World Application: Localization Testing

A practical use case for custom agents is localization. For teams working with multiple languages, content length often breaks layouts. By building a translation plugin, designers can instantly generate localized versions of their designs to identify where text expansion causes layout issues or scrolling problems. This allows for proactive design adjustments rather than reactive fixes during development.

Iteration and Governance

Once a plugin is created, it should be treated as a living tool. You can edit the agent's instructions to refine its behavior—for example, removing unnecessary "detect source language" steps if your team only ever works in English. For design managers, the key is to keep the toolset "thin." By requiring team members to vote on needed tools and demo them back to the group, you prevent the fragmentation of design workflows where different designers use different tools to achieve the same outcome.