◆ Figma

Build responsive layouts

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 taskBuild responsive layouts for key screens so they behave across phone, tablet, and desktop.…+
Build responsive layouts for key screens so they behave across phone, tablet, and desktop. Deliver the dashboard, settings page, and item detail views at 360, 768, and 1440 widths. Define breakpoints, describe how navigation collapses, and show how cards reflow. Annotate any layout decisions that affect component behavior. Ready for handoff by Monday morning.
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 this goes to front-end, make the responsive behavior obvious: put the breakpoint rules…+
Before this goes to front-end, make the responsive behavior obvious: put the breakpoint rules at the top of each file, show before-and-after frames for key reflows, highlight any components that change interaction (e.g., hover to tap), and call out where performance or image assets will need to swap at smaller sizes.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentUser tests show the primary action disappears into a 'more' menu on small screens and people…+
Mobile layout hides an action behind a menu and users miss it.
User tests show the primary action disappears into a 'more' menu on small screens and people can't find it. I need a diagnosis and the best next move. Is this a layout oversight, a priority decision, or an interaction problem? Recommend the single change to test that will surface the action on mobile without breaking desktop.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternFor three releases we shipped with layout regressions and frontend had to do manual CSS fixes.…+
Every responsive build requires last-minute CSS tweaks that delay release.
For three releases we shipped with layout regressions and frontend had to do manual CSS fixes. Where are we losing predictability and what habit should I change so responsive behavior is reliable? Suggest one design-time practice and one naming or spacing convention to prevent these recurring fixes.
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.