◆ Figma

Use graphics to enhance communication

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 taskTake the three key user flow diagrams from the 'Onboarding v2' file and put them into the 'Q3…+
Take the three key user flow diagrams from the 'Onboarding v2' file and put them into the 'Q3 Review Deck' presentation, making sure they're high-resolution and linked so if I update the source, they update in the deck.
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 share this wireframe with the new development team, add some simple annotations to…+
Before I share this wireframe with the new development team, add some simple annotations to explain the interactive elements and key states, especially for the 'Add to Cart' button and the checkout process, so they understand the intended behavior without a separate walkthrough.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe client just pushed back hard on the new navigation, saying it's too different from their…+
The client just pushed back hard on the new navigation, saying it's too different.
The client just pushed back hard on the new navigation, saying it's too different from their current site, even though our user testing showed it was clearer. I'm afraid if we revert, we lose all the usability gains. Priya from their marketing team is strongly against it, and I can't tell if she's speaking for the whole team or just her preference. What's the best way to diagnose their real concern and keep our design integrity?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep getting pulled into long meetings to explain basic design decisions to stakeholders who…+
I keep getting pulled into long meetings to explain basic design decisions.
I keep getting pulled into long meetings to explain basic design decisions to stakeholders who haven't looked at the files. It's draining my time and delaying my actual design work. What habit should I change to better communicate design intent upfront, so they arrive prepared and we can focus on strategic feedback, not just explaining the obvious?
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.