◆ Figma

Set constraints for responsiveness

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 product page responsive constraints set for three breakpoints. Open the product page…+
I need the product page responsive constraints set for three breakpoints. Open the product page file, set constraints on the hero image to stay pinned left and scale, pin the CTA to the bottom-right of its container, make the specs panel stretch horizontally with min and max widths, and verify at 320px, 768px, and 1440px. Save as ProductPage-Responsive and hand off to Ramesh by Wednesday end of day.
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 send this to Ramesh in engineering, make the responsiveness obvious: list which layers…+
Before I send this to Ramesh in engineering, make the responsiveness obvious: list which layers are pinned and which stretch at each breakpoint, call out any components that switch layout (column to row), and highlight elements that will break at narrow widths like multi-line captions or fixed-width icons. Flag anything that requires JS to behave correctly.
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 adjusted constraints and the header seems okay at 1024px yet on 375px the nav wraps and the…+
The header behaves fine at tablet width but collapses on mobile
I adjusted constraints and the header seems okay at 1024px yet on 375px the nav wraps and the search disappears. I’m presenting to founders tomorrow and can’t tell if this is a constraint issue, an overflow text problem, or a missing responsive variant. Which diagnostic checks should I run in order, what quick fixes will preserve the visual hierarchy, and when is it safer to add a mobile variant instead of fiddling with constraints?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross several launches engineers keep rebuilding constraints I left unset, which costs time…+
I repeatedly forget to set constraints and engineers recreate responsive rules
Across several launches engineers keep rebuilding constraints I left unset, which costs time and introduces subtle layout differences. What habit or checklist will stop me from leaving constraints undefined, and what small file-organization or naming convention makes it impossible to miss a layer that needs constraints before handoff?
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.