◆ Figma

Build component library

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 taskCreate the component library for our product team so designers and engineers use the same…+
Create the component library for our product team so designers and engineers use the same primitives. Include buttons, inputs, dropdowns, modals, cards, and spacing tokens. Define states for hover, focus, disabled, error, and loading. Add color and typography tokens, and a short notes page explaining when to use each component. Tag components for developer export. Completion by Wednesday noon.
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 call this a usable component library, make it easy for designers to find the right…+
Before I call this a usable component library, make it easy for designers to find the right control: put a usage example up top for each component, add a short do/don't note where common mistakes happen, surface variant props (size, tone) in a single grid, and flag anything missing accessibility attributes that would block developer implementation.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentEngineers pushed back: our buttons show five visual variants across screens. I can’t tell which…+
Engineering complains about inconsistent button variants.
Engineers pushed back: our buttons show five visual variants across screens. I can’t tell which are intended. Diagnose why our library let this happen and recommend the single immediate fix to stabilize button usage across the product—what change should I make to the library and how to enforce it in the next sprint.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery month new components show up that are slight copies of existing ones and engineers ignore…+
Library keeps accumulating duplicate components under different names.
Every month new components show up that are slight copies of existing ones and engineers ignore the library. Where are we leaking the work and what habit should I break? Recommend one governance rule and one lightweight review practice that will stop duplication and make the library the source of truth.
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.