◆ Figma

Set up design system

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 taskWe need a functioning design system for the mobile product before Monday’s planning. Create a…+
We need a functioning design system for the mobile product before Monday’s planning. Create a system file named Product Design System that contains color tokens for primary, secondary, success, warning, and neutral (use the brand palette I uploaded), text styles for H1, H2, H3, body, caption, and a grid layout 8pt baseline with a 360pt canvas for mobile. Build components for primary button, secondary button, input field, checkbox, and a simple top navigation. Link these components as libraries so the demo file can consume them.
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 share the system with the team, make it easy to use: surface the core tokens at the…+
Before I share the system with the team, make it easy to use: surface the core tokens at the top as named swatches, create clear naming for text styles (Investor/H1, Investor/Body), make component variants for size and state, and add a short guidelines page that explains when to use primary vs secondary buttons and the spacing rules. Call out any missing states or ambiguous token names that would confuse engineers.
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 published Product Design System and several designers are reporting their files still show…+
I published a library and now designers report mismatched components
I published Product Design System and several designers are reporting their files still show old buttons and text styles. I’m not sure whether they didn’t update the library, or whether I published with different component names that broke instances. What most likely happened and what immediate steps should I take to restore consistency across team files?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEach quarter we rebuild parts of the system and people keep using private overrides, creating…+
We keep treating the design system as a one-off deliverable and it breaks quickly
Each quarter we rebuild parts of the system and people keep using private overrides, creating drift between production files and the system. That wastes review time and causes inconsistent UI in releases. Which three process changes would reduce drift, speed adoption, and keep the system reliable for the next six months? Be specific about roles, cadence, and the smallest rules that must change.
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.