◆ Figma

Create and use 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 UI library update with the new badge component and version notes, then push the…+
Publish the UI library update with the new badge component and version notes, then push the library to the mobile and web files and notify the design and frontend squads. Ensure the token map for color and spacing is synchronized before publishing, confirm no breaking renames, and ask engineers to pull before their sprint demo on Tuesday.
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 library, make it easy for engineers and mobile designers to accept the…+
Before I publish the library, make it easy for engineers and mobile designers to accept the update. Show the diff for token changes, surface components that will change visually on mobile breakpoints, and flag any renames that require code changes. Provide a short upgrade note that tells engineers exactly which tokens to import and what known regressions to watch for.
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 just published a library update that renamed a spacing token and Android CI started failing.…+
I published a library and Android builds failed CI
I just published a library update that renamed a spacing token and Android CI started failing. I can’t see the build logs from here. What is the most likely mismatch between our tokens and the codebase, what immediate message should I send to the Android lead to buy time, and what’s the fastest rollback or patch I can make in the library to unblock builds?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEach library publish seems to create platform build failures or duplicated tokens and engineers…+
Library publishes keep breaking platform builds
Each library publish seems to create platform build failures or duplicated tokens and engineers complain they can’t rely on our releases. Are we failing on semantic token contracts, release communication, or on automation that should catch breaking changes? Recommend one change to publishing discipline, one automation check, and one cross-team habit to restore trust over the next two releases.
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.