◆ Figma

Publish and update libraries

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 taskPublish the updated component library to the team space and notify Sam in product and Leila in…+
Publish the updated component library to the team space and notify Sam in product and Leila in engineering that the library is ready for pull. Before you publish, open the design file, run the instance checker, and confirm there are no detached instances or missing tokens. Publish only the components tag that changes and attach a short changelog of what broke and what to migrate. Deadline Friday 5pm.
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 team library, make it easier for engineers to adopt: surface the breaking…+
Before I publish the team library, make it easier for engineers to adopt: surface the breaking token changes at the top, mark renamed components with the old name, and list migration steps for primary button and card variants. Flag any instances that will lose properties and suggest a safe fallback. Keep the changelog to five bullet points.
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 renamed button/primary to button/cta and adjusted spacing tokens; Sam and Leila say builds…+
I just pushed a variant rename and some tokens; two engineers flagged broken builds.
I renamed button/primary to button/cta and adjusted spacing tokens; Sam and Leila say builds broke and can’t find styles. Diagnose the most likely cause and give the fastest remediation to restore their builds with minimal rework, plus a short message I can send them explaining what I’ll do and when.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOver the past three months every library publish causes at least one engineer to open a ticket…+
We repeatedly break builds after library updates.
Over the past three months every library publish causes at least one engineer to open a ticket about missing styles. Where am I consistently failing — naming, migration notes, or test steps — and what three habits should I adopt so publishes stop breaking builds and engineers stop having to patch instances?
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.