◆ Figma

Bulk update component details

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskFind all instances of our old 'Primary Button' component across the 'Marketing Site Redesign'…+
Find all instances of our old 'Primary Button' component across the 'Marketing Site Redesign' file and update them to the new 'Call to Action Button v2' component. Ensure all text overrides are preserved.
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 hand off the 'Mobile App Onboarding' flow to development, go through all the screens.…+
Before I hand off the 'Mobile App Onboarding' flow to development, go through all the screens. Where we've used the legacy 'Header Bar' component, replace it with 'App Header v3'. Then, check if any of these changes break existing layouts or text styles, and flag those for my review.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur new design system components just dropped, and I need to update every live project. The…+
The new design system components just landed, and I'm supposed to update all our live projects.
Our new design system components just dropped, and I need to update every live project. The last time I did this, it broke a bunch of screens, and we had to scramble to fix it before a client demo. I'm worried about missing something critical again or introducing new bugs. What's the best way to roll these out without causing chaos, and what should I prioritize to minimize risk for the 'Client Dashboard' project?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly losing hours every week manually updating components across dozens of files…+
I spend too much time manually updating components across multiple files every time there's a design system change.
I'm constantly losing hours every week manually updating components across dozens of files whenever the design system evolves. It's tedious, error-prone, and pulls me away from new design work. What habit should I change to make these bulk updates less painful and more reliable, so I'm not always playing catch-up?
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.