◆ Figma

Automate design workflows

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 taskCreate a new variant for the 'Primary Button' component: 'State/Disabled'. It should have 50%…+
Create a new variant for the 'Primary Button' component: 'State/Disabled'. It should have 50% opacity and no hover effect. Add it to the main design system library.
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 start designing the new onboarding flow, set up a system that automatically generates…+
Before I start designing the new onboarding flow, set up a system that automatically generates all the different screen sizes for each frame I create. Also, make sure all new components I add automatically get added to the 'Onboarding' section of our local library.
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 just spent two hours manually updating 30 instances of our 'Card' component across five…+
I just spent two hours manually updating 30 instances of a component across multiple files, only to realize I missed one.
I just spent two hours manually updating 30 instances of our 'Card' component across five different project files because a small style change was requested. I'm exhausted and just found out I missed one instance on the 'Dashboard' page. I'm afraid of introducing inconsistencies and wasting even more time. What's the best way to quickly ensure all instances are updated and prevent this manual grind in the future?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently waste hours each week on repetitive, manual tasks like updating component states…+
I frequently find myself doing repetitive, manual updates to components or layouts across many files, wasting hours each week.
I consistently waste hours each week on repetitive, manual tasks like updating component states across multiple files or resizing frames for different breakpoints. This kills my focus on actual design problems. What habit should I change to automate these recurring, mind-numbing tasks so I can spend more time on creative work?
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.