◆ Figma

Archive Figma projects

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 taskArchive the 'Old Marketing Assets' project and move it to the 'Archive' team space. Confirm…+
Archive the 'Old Marketing Assets' project and move it to the 'Archive' team space. Confirm it's no longer visible to the active team.
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 Friday, go through all projects in the 'Explorations' team space that haven't been…+
Before Friday, go through all projects in the 'Explorations' team space that haven't been touched in over six months and move them to the 'Archive' team. For any project with a 'V1' or 'Legacy' tag, double-check with Sarah from Product if it needs to be retained for compliance before archiving.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur team's project list is a complete mess, making it hard to find active work, and I'm worried…+
Our team's project list is a mess, and I'm not sure what's safe to archive without losing important history or breaking links.
Our team's project list is a complete mess, making it hard to find active work, and I'm worried about hitting our storage limit. I want to clean it up by archiving old projects, but I'm afraid of accidentally deleting something vital or breaking links in our documentation. What's the best approach to identify projects that are truly safe to archive, and how do I ensure we don't lose any critical historical context for the 'Feature X' project?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur project list is always cluttered with old, inactive work, making it a nightmare to find…+
Our team always has a cluttered project list, making it hard to find current work and leading to confusion.
Our project list is always cluttered with old, inactive work, making it a nightmare to find what's current and leading to developers accidentally working on outdated files. It wastes time and creates unnecessary friction. What habit should I change to ensure our project spaces stay clean and organized, so everyone can quickly find the active projects they need?
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.