Three Figma habits that survive code review.

Most “Figma tip” lists optimize for the file you're editing today. The patterns that actually compound — that survive a year of new contributors, ten new component variants, and three rounds of dev handoff — are the boring ones. Three I never compromise on.

01 · Auto Layout for everything, even the static stuff.

The temptation: this card never reorders, why bother? The cost: six months from now, when product asks for one row of dynamic content above it, you're rebuilding spacing decisions from memory.

Auto Layout is the typed function signature of your design file. It doesn't make today's work faster. It makes tomorrow's pull request smaller.

If a designer can't change a single token and trust the spacing to recover, the file is fragile — regardless of how it currently looks.

02 · Layer names as documentation.

“Rectangle 297” is technical debt with no test coverage. Designers ship layer trees engineers have to interpret — every “Frame 12 / Group 4” is a question they'll ask in handoff.

The rule I follow: a fresh dev should be able to navigate the layer tree the way they'd navigate a component file. “Header / Nav / Items / Active” reads like the path it'll become in code. The naming isn't perfectionism — it's the minimum viable spec.

03 · Tokens, not styles.

Shared styles solve the problem of “change blue once, update everywhere.” Variables solve the problem of “what does blue mean?”

A “Primary / 600” token survives a brand refresh. A “#1F39B2” style locks you to a specific hex in 47 places. Scale isn't a future concern — it's three files and twelve handoffs from now.

The pattern underneath

These three habits look unrelated, but they answer the same question: what would future-me want to inherit?

Senior design isn't faster keystrokes. It's giving the next person a file they can extend without archaeology.