◆ Figma

Resolve design feedback

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 taskResolve the unblockers on the checkout redesign: accept the legal copy changes that don’t…+
Resolve the unblockers on the checkout redesign: accept the legal copy changes that don’t affect layout, push the promo code edge case to a follow-up ticket, confirm the success state with payments, and tell Priya in product and Daniel in payments the final decision and next ticket owners.
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 close feedback on the checkout, make the resolution easy to approve: summarize each…+
Before I close feedback on the checkout, make the resolution easy to approve: summarize each open issue with our position, mark which require design changes vs engineering work, show the trade-off for each choice, and recommend the minimal changes to ship on Monday.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentLegal handed a rewrite this morning that would push our launch past the committed date. I am…+
Legal demanded a rewrite that would delay launch
Legal handed a rewrite this morning that would push our launch past the committed date. I am the designer, legal lead is Omar, and the product manager pledged the current launch. I don’t know whether Omar will accept a narrower scope or insist on full rewrite. What’s the likeliest posture and the best next move to keep the launch date?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe repeatedly delay launches because small unresolved feedback accumulates into big scope…+
Small feedback threads keep delaying launches
We repeatedly delay launches because small unresolved feedback accumulates into big scope changes. I coordinate launches across product, legal, and payments. Which habit should I change to stop tiny comments from derailing release dates and how do I enforce it?
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.