◆ Figma

Search and replace styles

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All Figma tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskSearch the file for all uses of the old gray/600 color and replace them with the new…+
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.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore 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.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI bulk-searched and replaced a text style and several captions now read like body text. I need…+
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.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternGlobal search-and-replace keeps changing tone and hierarchy across dozens of screens. Where am…+
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?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Figma's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.