◆ Figma

Use auto-layout for frames

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 the dashboard frames rebuilt with consistent auto-layout so components resize…+
I need the dashboard frames rebuilt with consistent auto-layout so components resize predictably. Start with the main dashboard frame and convert its columns and cards to auto-layout, keep current padding and gaps, ensure nested buttons use horizontal auto-layout, and check that text fields don't collapse. Confirm visually in the 13” breakpoint and send back a single file named Dashboard-AutoFrame by Thursday noon.
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 engineers, make the layout easy to reuse and debug: surface the…+
Before I hand this to engineers, make the layout easy to reuse and debug: surface the auto-layout direction and padding at the frame level, move fixed-width elements into separate non-auto frames, flag where nested auto-layouts will cause height jumps, and call out any text styles that will overflow. Produce a short list of three things that would make a reviewer hesitate to reuse these components.
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 switched the left column of the dashboard into auto-layout and several cards expanded…+
I converted one column to auto-layout and now the card heights jumped unexpectedly
I switched the left column of the dashboard into auto-layout and several cards expanded vertically. Priya on front-end will have to reconcile this and we’re running into Friday’s demo. I’m not sure which nested component is forcing the stretch or whether I should revert just that column. What likely caused the height change, what should I inspect first, and what’s the fastest safe rollback to meet the demo?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOver the last three sprints I rebuild dashboard, settings, and reports frames from scratch…+
I keep rebuilding similar frames rather than reusing a consistent auto-layout pattern
Over the last three sprints I rebuild dashboard, settings, and reports frames from scratch instead of reusing an auto-layout pattern. That wastes time and creates inconsistencies for engineering. What habit should I change so I stop duplicating work, and what practical steps make a single reusable auto-layout system that designers and engineers will actually adopt?
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.