The foundation is set: You’ve refined your assets, documented their intended use, and added examples and guidelines to help the agent apply your design system.
Over time, new needs will emerge: a component needs another state, a convention changes, or a new pattern starts appearing more frequently.
The Figma agent can help you make these updates to your library. It can make changes across multiple assets, find reusable patterns in product designs, and review updates before publishing.
Update library assets in bulk
Changes to naming, sizing, variants, or styles may need to be applied across many components. The agent can help you find the affected assets and make the same change consistently. This is also useful when you bring a component from another design file into your library and need to align it with existing conventions.
Try prompts such as:
- “Turn the selected icons into components, name them according to our icon convention, and arrange them alphabetically.”
- “Create a 16 px version of this 24 px icon set. Adjust the stroke width and names to match our 16 px icons.”
- “Remove shadow styles from the components in this set.”
- “Rename the default layer names on this page to follow our naming convention.”
Tip: For more ways the agent can help with file cleanup tasks, see Cut down on busywork.
Find patterns worth adding to the system
Product designs can reveal patterns that your library does not yet capture. Ask the agent to compare selected screens or components, identify recurring layouts and values, and suggest assets that could make those patterns reusable. Review the proposal before adding anything to the library: a repeated design choice may be intentional, temporary, or specific to one product area.
For example, you might ask:
- “Compare the cards in these screens. Which parts are consistent, and what would a reusable card component need to support?”
- “Find colors and type sizes used on this page that are not represented by styles or variables in the connected library.”
- “Review these designs for repeated patterns that could become components or states. Show where each pattern appears before suggesting changes.”
- “Compare these CSS variables with the variables in this Figma library and list any gaps.”
- “Grab the latest designs from [design file] and the discussion from [FigJam file] and annotate the designs with the discussions on which patterns we should systematize.”
Once you decide a pattern belongs in the system, the agent can help draft a component or variable collection as a starting point. Check that the result reflects the intended usage across the product, not just the examples you selected.
Review a library update before publishing
Before publishing changes, use the agent as an initial reviewer. It can help surface missing states, inconsistent construction, unclear names, or documentation gaps that are easy to overlook when you have been working in the file for a while.
Try asking:
- “Review this component set for missing states or variants. Explain where each would be needed.”
- “Compare this component with similar components in the library. What is inconsistent?”
- “Are any components redundant or difficult to distinguish by name or purpose?”
- “What should I review before publishing this library update?”
Treat the agent's findings as suggestions to inspect, then decide which changes belong in the system.
Tip: Before publishing an update, you can also use Check designs—available on the Organization and Enterprise plans—to scan your design file for inconsistencies with your design system.
Check designs helps you identify:
- Incorrect colors
- Components, variables, and styles from incorrect libraries
- Hardcoded values that should be variables