The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Apply the approved typography system to the Marketing and Dashboard screens in the file Project UI…
Execute — do the immediate task
+Apply the approved typography system to the Marketing and Dashboard screens in the file Project UI Kit. Replace ad-hoc font sizes with the defined styles: Heading 1, Heading 2, Body, Caption, and Button. Ensure responsive scaling for tablet and phone breakpoints, fix any line-height or letter-spacing issues that break layout, and publish the updated styles to the Team Library before tomorrow's demo.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before publishing the type styles to the library, make approvals fast: surface where current…
Improve — make it easier to accept
+Before publishing the type styles to the library, make approvals fast: surface where current screens use local text overrides, show instances where line-height or scaling will cause truncation on smaller viewports, and flag any components that rely on exact pixel sizes. Highlight anything that would make a reviewer hesitate to accept the new styles.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Decide — diagnose the stuck moment
+I applied the Heading 1 style to multiple headers and now some cards overflow on tablet layouts.…
Decide — diagnose the stuck moment
+After switching several headers to Heading 1 style, cards overflow on tablet
I applied the Heading 1 style to multiple headers and now some cards overflow on tablet layouts. I’m not sure whether the problem is applying a desktop-scale style to a responsive component or an incorrect auto-layout constraint. What should I check first to diagnose whether this is a style scaling issue or a layout setting, and what quick fix will unblock the demo?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Every few sprints a typography cleanup creates layout regressions: text truncates, cards reflow,…
Become — change the pattern
+Typography updates keep causing layout regressions across screens
Every few sprints a typography cleanup creates layout regressions: text truncates, cards reflow, and builds miss QA. Where should I change my process so typography changes land without breaking interfaces? Propose a small pre-publish routine and a habit for communicating scale changes to engineers and PMs.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
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.