◆ Figma

Edit multiple objects simultaneously

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 taskSelect all the primary call-to-action buttons across the 'Marketing Landing Pages' file and…+
Select all the primary call-to-action buttons across the 'Marketing Landing Pages' file and change their fill color to #007bff. Ensure the text color remains white.
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 acceptI need to adjust the padding on all form fields in the 'Checkout Flow' file. Before I do, make…+
I need to adjust the padding on all form fields in the 'Checkout Flow' file. Before I do, make sure the changes are consistent across all breakpoints, don't break existing alignments, and are easily reversible if the client changes their mind.
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've applied 'Inter Bold' to all H1 and H2 headers in the 'Blog Redesign' file, but now some…+
I've applied a new font to all headers, but some text layers are now overflowing their containers, and I'm not sure which ones.
I've applied 'Inter Bold' to all H1 and H2 headers in the 'Blog Redesign' file, but now some text layers are overflowing their containers, and I can't easily spot all of them. I'm afraid of missing one and having it go live looking broken. I can't tell if this is a consistent issue or just a few outliers. What's the likely diagnosis, and what's the best next move to quickly identify and fix all affected elements?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI constantly find myself manually resizing elements after making global style changes, like…+
I constantly find myself manually resizing elements after making global style changes.
I constantly find myself manually resizing elements after making global style changes, like font updates or padding adjustments. This wastes a lot of time and introduces inconsistencies. What habit should I change to make these large-scale edits more efficient and less prone to manual errors?
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.