◆ Figma

Apply typography styles

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
See the prompt↓All Figma tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskApply the approved typography system to the Marketing and Dashboard screens in the file Project…+
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.
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 publishing the type styles to the library, make approvals fast: surface where current…+
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.
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 applied the Heading 1 style to multiple headers and now some cards overflow on tablet…+
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?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery few sprints a typography cleanup creates layout regressions: text truncates, cards…+
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.
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.