◆ Figma

Swap component variants

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 taskI need the button variant swapped across the checkout screens so the ‘primary/active’ style…+
I need the button variant swapped across the checkout screens so the ‘primary/active’ style shows where the user can progress. Replace the rounded-blue variant with the filled-blue-primary variant on Checkout Step 1, Payment Review, and Order Confirmation, then check the interactions on desktop and mobile to ensure hover and pressed states still map to the correct variants. Complete by Thursday noon and flag any overrides you can’t reconcile.
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 change variants across the file, make it obvious to reviewers which screens will…+
Before I change variants across the file, make it obvious to reviewers which screens will change and why. Show the current component usage count, surface the visual difference between rounded-blue and filled-blue-primary at 1x and 2x, and list any instances with local overrides or detached instances that would break if I swap. Highlight anything that would affect the visual hierarchy on Payment 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 momentI swapped the global button variant on the Payment Review frame and the CTA vanished in one…+
I swapped a variant and the payment button disappeared
I swapped the global button variant on the Payment Review frame and the CTA vanished in one breakpoint. The engineering handoff is Friday and I can’t tell if this is a missing instance, a renamed variant, or an override hiding the layer. Which is most likely, what should I check in the next five minutes, and what’s the safest immediate rollback so the handoff stays on schedule?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery time I replace a component variant across the product, screens break because of…+
I keep breaking screens when swapping variants
Every time I replace a component variant across the product, screens break because of overrides, naming drift, or detached instances. I lose time finding and fixing each case and stakeholders start to distrust mass updates. Where are we most likely failing on naming, library governance, or release steps, and what three habits should I adopt this quarter to reduce these firefights by 80%?
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.