◆ Figma

Rename and organize layers

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 Product UI file and rename layers so an engineer can find assets: change…+
Go through the Product UI file and rename layers so an engineer can find assets: change 'rect12' to 'Header / Background', 'txt7' to 'Header / Title', and 'btn3' to 'CTA / Primary'. Group related layers into folders named Header, Hero, and Form, and pin a note for Lina in engineering where we removed nested groups that affect export.
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 the file to frontend, tidy the layer tree so they stop asking questions: collapse…+
Before I hand the file to frontend, tidy the layer tree so they stop asking questions: collapse decorative layers into a single group, name interactive elements with > notation (Header > CTA Primary), and flag any layers that use masks or effects that will break SVG export.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentTom from engineering opened the file and couldn't locate the action icon because the layers are…+
An engineer complained they couldn't find the icon they needed in the file.
Tom from engineering opened the file and couldn't locate the action icon because the layers are all generically named. He needs the icon exported at 2x and 1x. I don't know which layers are actually used versus legacy. What's the fastest way to identify the active icon instance, rename it clearly, and confirm exports without combing the entire file?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe hand off files with inconsistent naming, hidden legacy layers, and nested masks; engineers…+
Layer chaos slows handoff every sprint.
We hand off files with inconsistent naming, hidden legacy layers, and nested masks; engineers waste hours asking for clarifications. Is the root cause sloppy naming at creation, absence of a file template, or poor component discipline, and what one habit should the design team adopt so future handoffs take minutes not days?
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.