◆ Figma

Export CSS and code snippets

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskI need the CSS and code snippets for the login component so engineers can integrate it. Export…+
I need the CSS and code snippets for the login component so engineers can integrate it. Export the CSS for the container, inputs, button, and the responsive breakpoints used in Release‑v1; paste the snippets into a document and label which selector corresponds to which layer name.
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 send code to the devs, make it easy to copy: surface the class names and generated CSS…+
Before I send code to the devs, make it easy to copy: surface the class names and generated CSS at the top, show the responsive media queries, and flag any styles that rely on tokens not yet in the global styles. If a value is tokenized, replace it with the token name; if not, suggest the token to create.
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 CSS for the header and it uses color tokens that are not in the shared library; I…+
I exported CSS but it references tokens that don't exist in the shared library.
I exported CSS for the header and it uses color tokens that are not in the shared library; I worry engineers will create ad‑hoc values and lose consistency. I cannot tell whether those tokens were supposed to be added earlier or if the current palette is temporary. Should I ask the design lead to publish the tokens, send the raw values to engineering, or create provisional token names? Recommend the best immediate action and the wording for a quick note to engineering.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe keep shipping CSS with hardcoded values so engineering creates their own tokens and we…+
Handing off code snippets repeatedly causes devs to reimplement tokens.
We keep shipping CSS with hardcoded values so engineering creates their own tokens and we fracture the design system. Which habit should change: stop exporting until tokens exist, add a mandatory tokenization step, or pair with an engineer during handoff? Recommend one habit to adopt, two concrete enforcement steps, and a one‑line policy to add to the release checklist.
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.