Search and replace styles — AI Prompts for Figma

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

Search the file for all uses of the old gray/600 color and replace them with the new neutral/700…

Search the file for all uses of the old gray/600 color and replace them with the new neutral/700 token across components and artboards. Before committing, verify button hover, disabled, and border states still meet contrast and confirm no text tokens are replaced wrongly. Commit the change with a note referencing ticket BX-42 and ping accessibility@company for a quick review.

Improve — make it easier to accept

Before I run a global replace on styles, make it safe for reviewers: produce a list of affected…

Before I run a global replace on styles, make it safe for reviewers: produce a list of affected components, surface places where replacing a color or type token would alter hierarchy (for example, body to caption), and flag cases where a swap could break accessibility contrast. Recommend any manual checks for interactive states and suggest wording for the commit message.

Decide — diagnose the stuck moment

I bulk-searched and replaced a text style and several captions now read like body text. I need to…

I replaced a text style and now secondary text looks like body copy.

I bulk-searched and replaced a text style and several captions now read like body text. I need to know the likely mistake I made and the fastest way to restore correct hierarchy only where it matters for screens in the next release. Also give a short note I can send to the UX writer and product owner explaining what I’ll revert and why.

Become — change the pattern

Global search-and-replace keeps changing tone and hierarchy across dozens of screens. Where am I…

I repeatedly misapply global style replacements and cause visual regressions.

Global search-and-replace keeps changing tone and hierarchy across dozens of screens. Where am I consistently going wrong — overbroad search terms, not scoping by component, or missing state checks — and what three practices should become standard before any mass style change to prevent future regressions?

Next to this one

Other interface design work people do in Figma.

Prototype user flows Publish and update libraries Record prototype flows Rename and organize layers Resolve design feedback Set constraints for responsiveness Set file permissions and access Set up design system Share prototypes with stakeholders Swap component variants

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.

The rest of the map

Same library, five ways in.

Work Atlasthe whole map, interactive Careers1,949 jobs and their real tasks Soft skillsthe human part of the work Activities500 things people do Prompt Librarybrowse every prompt