◆ Figma

Measure spacing and dimensions

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 exact spacing and dimensions across this screen before I hand it to front‑end. Measure…+
I need exact spacing and dimensions across this screen before I hand it to front‑end. Measure padding, margin, and component heights for the header, hero card, and the three list items; put pixel values and the source frame name in a short table. Check the mobile and desktop frames named Release‑v1 and Release‑v1‑mobile and flag any mismatches over 4px.
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 pass specs to engineering, make the spacing obvious: surface the main vertical rhythm…+
Before I pass specs to engineering, make the spacing obvious: surface the main vertical rhythm at the top, show component heights next to each element, and highlight any gaps over 8px that break the grid. Call out where padding is inconsistent between Release‑v1 and Release‑v1‑mobile and suggest the single change that fixes both.
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 just found the header padding is 12px on Release‑v1 and 20px on Release‑v1‑mobile; I am…+
I compared the header padding between frames and found different numbers.
I just found the header padding is 12px on Release‑v1 and 20px on Release‑v1‑mobile; I am afraid engineers will pick the wrong one and the build will look off. I cannot tell whether the mobile spec was meant to be different or someone adjusted it by mistake. Do I enforce 12px, match mobile to desktop, or ask the designer who touched the mobile frame? Recommend the most defensible next move and a one‑sentence message to the designer.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross releases I keep losing time reconciling small spacing differences that break CSS…+
Every handoff has repeated spacing inconsistencies across frames.
Across releases I keep losing time reconciling small spacing differences that break CSS variables. Where should I change my habit: stop trusting copied frames, add a short prehandoff checklist, or gate handoffs with a quick spacing audit? Recommend the single habit to adopt, how to enforce it in two steps, and a one‑line rule to put in the design handoff note.
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.