◆ Figma

Manage 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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskConsolidate the card component into three variants: compact, default, and expanded. Migrate all…+
Consolidate the card component into three variants: compact, default, and expanded. Migrate all product list and dashboard instances to the default variant, update overrides for image aspect ratios, and ensure interactions for expand/collapse map to the expanded state. Finish migration by Monday and report any frames that reference a detached master or a renamed variant.
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 reorganize card variants, make it easy for PMs and engineers to approve the change.…+
Before I reorganize card variants, make it easy for PMs and engineers to approve the change. Show a matrix of where compact versus default currently appears, surface places where local overrides change padding or shadows, and flag any components that rely on the old expanded layout for JS hooks. Call out the complexity cost of every instance that will need manual adjustment.
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 merged three card variants into default and compact, and the analytics dashboard now shows…+
We merged variants and one dashboard lost its spacing
I merged three card variants into default and compact, and the analytics dashboard now shows collapsed spacing on several rows. I’m not sure if the issue is a padding override or that the instance accidentally switched to compact. What are the likely causes, what quick view should I open to diagnose the problematic instances, and how do I revert only those instances without undoing the whole merge?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOver the past six months we keep refactoring component variants and each time it creates new…+
Variant churn causes repeated visual regressions
Over the past six months we keep refactoring component variants and each time it creates new visual regressions and extra QA cycles. Is the pattern coming from poor naming, insufficient migration checks, or a lack of stable tokens? Recommend a practical convention and one enforcement step we can add to our release checklist so variant churn stops costing us sprints.
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.