◆ Figma

Clean up Figma files

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 taskGo through the 'Marketing Landing Page' file and organize all the unused components and layers…+
Go through the 'Marketing Landing Page' file and organize all the unused components and layers into a 'Archive' page, then delete any duplicate styles or colors that aren't being used anywhere.
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 hand off the 'Mobile App Redesign' file to the developers, run through it and make…+
Before I hand off the 'Mobile App Redesign' file to the developers, run through it and make sure all layers are properly named, components are clearly defined, and there are no stray elements outside the frames, so they don't waste time deciphering my mess.
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 junior designer just created a dozen new text styles for a single project, completely…+
The new junior designer just created a dozen new text styles for a single project.
The new junior designer just created a dozen new text styles for a single project, completely ignoring our established design system. I'm afraid if I don't address it quickly, our entire file will become a chaotic mess, but I also don't want to demotivate them. The project lead needs this by Friday. What's the best way to gently correct this without making them feel incompetent, while still enforcing our standards?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternMy design files consistently become bloated and hard to navigate by the end of a project,…+
My design files consistently become bloated and hard to navigate by the end of a project.
My design files consistently become bloated and hard to navigate by the end of a project, making handoffs a nightmare and slowing down iterations. I waste too much time searching for elements or cleaning up before reviews. What habit should I change to maintain cleaner, more organized files from the start, so I'm not scrambling at the finish line?
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.