◆ Figma

Manage Figma administration

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 taskAdd the new 'Brand Guidelines' library to the 'Marketing Team' project and ensure all designers…+
Add the new 'Brand Guidelines' library to the 'Marketing Team' project and ensure all designers in that team have editor access. Archive the old 'Logo Assets' library so it doesn't get used by mistake.
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 archive the 'Legacy Components' library, check if any active projects are still linked…+
Before I archive the 'Legacy Components' library, check if any active projects are still linked to its assets. If so, suggest the best way to migrate those projects to the new 'Design System V2' library without breaking their current designs or requiring a full manual audit.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe new intern, Alex, just accidentally deleted the main 'Button' component from our 'Core UI…+
The new intern just accidentally deleted a critical component from the 'Core UI Kit' library, and I'm not sure how quickly we can restore it without disrupting ongoing work.
The new intern, Alex, just accidentally deleted the main 'Button' component from our 'Core UI Kit' library. It's used across dozens of active projects. I'm afraid of the cascading impact and how long it will take to restore it correctly without breaking existing files or causing a panic with the development team who are pulling from it right now. What's the likely diagnosis of the problem, and what's the best next move to minimize disruption?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently find myself manually updating component properties like color or typography across…+
I frequently find myself manually updating component properties across multiple files when a global change is needed.
I frequently find myself manually updating component properties like color or typography across dozens of individual files whenever a global brand change happens. This is incredibly time-consuming and prone to errors, often leading to inconsistencies that the QA team flags later. What habit should I change to ensure these global updates are managed more efficiently and reliably across our entire design system?
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.