Rename and organize layers

Rename and organize layers in Figma — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
Go through the Product UI file and rename layers so an engineer can find assets: change 'rect12' to…
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.

Improve — make it easier to accept

+
Before 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.

Decide — diagnose the stuck moment

+
Tom from engineering opened the file and couldn't locate the action icon because the layers are all…

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?

Become — change the pattern

+
We hand off files with inconsistent naming, hidden legacy layers, and nested masks; engineers waste…

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?

Next to this one

Other interface design work people do in Figma.

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.