◆ Figma

Present designs in meetings

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 taskI need to present the new onboarding flows at Wednesday’s product review to the head of…+
I need to present the new onboarding flows at Wednesday’s product review to the head of product, two engineering leads, and Maya from growth. Walk through screens in order, call out the two places we changed user text and the performance assumptions behind them, pause for questions after each flow, and close by asking for a go/no-go decision and any blocking technical concerns.
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 present to the group, make these slides easy for non-designers to follow: put the…+
Before I present to the group, make these slides easy for non-designers to follow: put the conversion lift estimate on the first slide, mark which screens require backend changes, highlight two usability trade-offs we considered, and list the single ask for engineering and the single ask for growth so reviewers can approve quickly.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentWe just finished the walkthrough and the engineering lead looked confused about the payment…+
I finished the walkthrough and the engineering lead looked confused
We just finished the walkthrough and the engineering lead looked confused about the payment step. I am the designer, the lead is Sam, and we have a Friday build deadline. I don’t know whether Sam is worried about technical feasibility, scope, or risk to stability. What’s the most likely diagnosis and the best next move to get a clear go/no-go?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery demo turns into a long feature debate and we leave without concrete decisions. I run…+
Presentations drift into feature debate and miss decisions
Every demo turns into a long feature debate and we leave without concrete decisions. I run product demos for the PM, two eng leads, and growth. Which habit should I change to keep meetings focused and how should I enforce it so reviewers leave with clear actions?
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.