◆ Figma

Annotate designs for developers

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 these screens ready for handoff to the engineering squad. Annotate each artboard with…+
I need these screens ready for handoff to the engineering squad. Annotate each artboard with component names, prop values, and the exact spacing system used; attach the exported SVGs and the font files to the same project. Send the packet to Marco in iOS and to Aisha in Android for review, in that order, with a Tuesday noon deadline — check that every interactive state is documented first.
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 hand this to the engineers, make the annotations impossible to miss. Put the primary…+
Before I hand this to the engineers, make the annotations impossible to miss. Put the primary interaction notes next to the tappable elements, surface the exact color and token names at top of each frame, mark anything that deviates from our design system with a red flag and a one‑line rationale, and list the assets every platform needs on a single sheet.
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 got a message: Marco says he can’t implement the login because several…+
Developer flagged missing states on the login flow
We just got a message: Marco says he can’t implement the login because several micro‑interactions and error states aren’t documented. The sprint is blocked, the backend lead is waiting, and I don’t know which states he expects vs. what we actually designed. What likely gaps caused this and what’s the fastest, lowest‑risk way to fix the handoff so Marco can keep going?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery release cycle we lose two days to engineers asking for clarifications on interaction…+
Handoffs repeatedly cause dev rework
Every release cycle we lose two days to engineers asking for clarifications on interaction states and responsive rules. I’m burning time recreating annotations and apologizing to product. Which three habits should I change in my design workflow so handoffs stop being the bottleneck and engineers trust the files coming from me?
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.