Set constraints for responsiveness

Set constraints for responsiveness in Figma — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
I 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.

Improve — make it easier to accept

+
Before I send this to Ramesh in engineering, make the responsiveness obvious: list which layers are…
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.

Decide — diagnose the stuck moment

+
I 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?

Become — change the pattern

+
Across several launches engineers keep rebuilding constraints I left unset, which costs time and…

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?

Next to this one

Other interface design work people do in Figma.

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.