Design systems need constant maintenance that is easy to postpone: cleaning up names, verifying tokens, refreshing docs, and finding where product work has drifted from the library. As teams build faster, that drift gets harder to see. The quality of an agent's output depends on the context it receives, and much of that context lives in the design system. Figma's agent can absorb a good share of this upkeep and can apply a system's rules and conventions when new work is created. The examples below show where teams are using it.

Documentation as an agent task

Documentation serves several audiences—designers picking a component, developers preparing handoff—and it clarifies how the system should be used so teams apply it consistently. Once the behavior of a component is settled, the agent can draft the documentation and keep it current as the system changes.

Prompts to give the agent:

  • Write do's and don'ts for using a component.
  • Show visual examples of variants, properties, and configurations.
  • Recommend component APIs for handoff, such as merging booleans into enums, removing unnecessary hover states, or promoting buried child properties.

Ian Guisard, a product designer at Uber, uses the agent with a set of skills he built to document components across Uber's seven platforms. Running /create-api produces an organized, developer-friendly description of how a component works; /create-color produces a color spec showing which design token each part uses across variants and states. Developers get the details without searching the Figma file or returning to designers for clarification.

Keeping product screens on-system

A single screen can draw components and tokens from several libraries, which makes a manual review slow. The agent can inventory what a screen uses and trace each item back to its library.

Find drift before it spreads

Suppose a designer preparing a checkout screen builds a "Save for later" button from scratch instead of using the system's button. The agent can check the screen against the design library, flag the duplicate of the existing Button/Secondary component, and note any hard-coded color or spacing value in place of a current token—leaving time to swap in the production component and token before the design moves forward.

Replace components and tokens in bulk

Existing product screens and AI-generated designs can fall out of sync with product components and tokens, and fixing them by hand means replacing parts one at a time. You can @-mention a specific component or token in a prompt to have it replaced across a design in bulk, or ask the agent to find and replace components from a specified library and then review the changes.

Paavan Buddhdev, a product designer at the AI notetaking app Granola, brings existing screens from the Granola app into Figma with the Figma Chrome extension. Buttons and other elements arrive disconnected from Granola's design system; rather than replacing each manually, he selects an imported button and asks the agent to swap in the matching design system button.

Give the agent your system's rules

Once existing work is back on the system, the next concern is keeping new work on-system. Guidelines added to a published library capture the intent, rules, and patterns behind the system for the agent to use. Because that context is included automatically whenever the library is attached, designers don't have to restate the same instructions in every prompt.

Cleanup work the agent can absorb

Small inconsistencies accumulate quickly, are tedious to fix, and can weaken trust in the system—pushing product builders to work around it instead. The agent can take on some of that upkeep.

Standardize naming

Renaming a single component is simple; reconciling a whole library where the same state is called hover, hovered, and mouse-over is not. Prompts to give the agent:

  • Take stock of the names currently used across the system.
  • Surface names that have drifted apart, like small and sm, then reconcile them to one convention, like small.
  • Apply a naming decision already made across the entire library at once.
  • Replace generic asset names like icon_1 or icon_2 with descriptive ones like linkedin_icon or tiktok_icon.
  • Create a record of what was renamed so the changes can be carried into code.

Verify token adoption

As a library grows, knowing whether every component still uses the right tokens becomes harder. The agent can inspect a component's values and check whether they are tied to design tokens, and it can create annotations showing which tokens a component uses. It can surface cases like a button component using 8 px for icon spacing instead of the shared spacing token the rest of the library uses. Teams that want to run the same check on a schedule can package the steps into a repeatable workflow with a skill.

Availability

The Figma agent is available to Full seat users on Professional, Organization, Enterprise, and some Education plans, with limited availability on the Starter plan. Collab, Dev, and View seats can use the agent in their drafts.