◆ Figma

Create design tokens

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 taskCreate a set of design tokens for the product's component library used by engineering. Extract…+
Create a set of design tokens for the product's component library used by engineering. Extract spacing, border-radius, primary and neutral color values, font sizes and weights, and elevation shadows from the file named System Tokens v2. Export them as JSON and CSS variables, include clear names that match our component props (token names must match how engineers refer to them in code), and drop the files into the Shared Assets folder by Wednesday.
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 publish the tokens to the team, make them easy for engineers to adopt: surface the…+
Before I publish the tokens to the team, make them easy for engineers to adopt: surface the token-to-prop mapping at the top, group tokens by usage (layout, typography, color, elevation), flag tokens that are duplicates or near-duplicates, and call out any tokens that will break existing components if renamed. Point out anything that would make an engineer hesitate to import them.
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 exported a token JSON and engineers say the spacing tokens don't align with the variable…+
Engineers reported the spacing tokens don't match CSS variable names in the repo
I exported a token JSON and engineers say the spacing tokens don't align with the variable names in the repo's component library. I don't know whether the mismatch came from an earlier rename in the design file or from my export settings. What’s the most likely cause and how should I correct it with minimal churn so we don't block the sprint? Should I rename tokens to match code, update the repo, or provide a compatibility map?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOver several releases we keep breaking components because token names change or values drift…+
We keep shipping token changes that force code churn and regressions
Over several releases we keep breaking components because token names change or values drift without coordination. This costs engineering time and trust. What habit should our design team adopt to stop this? Suggest a governance routine or a minimal naming convention and a release checklist that prevents accidental renames and makes token updates predictable.
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.