456: Should Designers Name Their Layers?
Episode
32 min
Read time
2 min
Topics
Design & UX, Artificial Intelligence, Software Development
AI-Generated Summary
Key Takeaways
- ✓Design systems require naming discipline: When building component libraries like YouTube's design system, layer names directly impact usability for other designers. Component names, properties, and variants must be clearly labeled because the layers themselves are the shipped product that other teams consume, making naming non-negotiable for systems work.
- ✓Naming aids structure and future retrieval: Naming layers forces designers to think about grouping logic and hierarchy, not just labels. When returning to files months later or using Figma's search feature (command-f), well-named layers enable quick navigation. The practice creates self-documenting files that explain design intent without requiring the original designer's presence.
- ✓Exploratory work benefits from loose structure: During early ideation phases, strict naming conventions can create premature optimization that locks designers into specific concepts too early. The mental overhead of maintaining accurate names while rapidly iterating can slow down the creative process. FigJam's lack of a layers panel demonstrates how freeform tools intentionally avoid structural constraints during brainstorming.
- ✓Engineer handoff value depends on implementation approach: Modern CSS frameworks like Tailwind use utility classes instead of semantic naming, reducing the importance of layer names in code translation. Engineers primarily need structural information (how elements nest and align) rather than descriptive labels. The actual div elements rarely inherit Figma layer names, making structure more valuable than nomenclature.
- ✓AI tools increase naming importance: Emerging AI design tools and Figma-to-code generators rely on layer names to infer designer intent and generate accurate output. As automation becomes more prevalent, well-named layers provide the context these systems need. Diagram and similar tools are developing AI layer naming to automate this process, suggesting computers may eventually handle naming hygiene automatically.
What It Covers
Brian Lovin and Marshall Bock debate whether designers should name their layers in Figma files. The discussion covers organizational hygiene, collaboration with engineers, design system maintenance, and when layer naming matters versus when it becomes premature optimization that slows down exploratory design work.
Key Questions Answered
- •Design systems require naming discipline: When building component libraries like YouTube's design system, layer names directly impact usability for other designers. Component names, properties, and variants must be clearly labeled because the layers themselves are the shipped product that other teams consume, making naming non-negotiable for systems work.
- •Naming aids structure and future retrieval: Naming layers forces designers to think about grouping logic and hierarchy, not just labels. When returning to files months later or using Figma's search feature (command-f), well-named layers enable quick navigation. The practice creates self-documenting files that explain design intent without requiring the original designer's presence.
- •Exploratory work benefits from loose structure: During early ideation phases, strict naming conventions can create premature optimization that locks designers into specific concepts too early. The mental overhead of maintaining accurate names while rapidly iterating can slow down the creative process. FigJam's lack of a layers panel demonstrates how freeform tools intentionally avoid structural constraints during brainstorming.
- •Engineer handoff value depends on implementation approach: Modern CSS frameworks like Tailwind use utility classes instead of semantic naming, reducing the importance of layer names in code translation. Engineers primarily need structural information (how elements nest and align) rather than descriptive labels. The actual div elements rarely inherit Figma layer names, making structure more valuable than nomenclature.
- •AI tools increase naming importance: Emerging AI design tools and Figma-to-code generators rely on layer names to infer designer intent and generate accurate output. As automation becomes more prevalent, well-named layers provide the context these systems need. Diagram and similar tools are developing AI layer naming to automate this process, suggesting computers may eventually handle naming hygiene automatically.
Notable Moment
The hosts reveal their opposing design philosophies stem from their roles: Marshall maintains YouTube's design system where layers are the product shipped to other designers, while Brian builds products where only the final implementation matters to users. This role difference explains why Marshall views naming as essential hygiene while Brian sees it as situational optimization.
Episode Transcript
Still recovering from editing that interview. Yeah. Mister, we should do more guest episodes. These are these are easy for us. We just have a conversation with somebody. I thought it would be easier. Q three extra days of editing. Welcome to episode 456 of the design details podcast. I'm fighter number one in the right corner. Brian Levin. Player two has entered the game. Hi. I'm Marshall Bach. We'll go back for another episode. Brian, what do we got on the docket for today? We're gonna fight today, Marshall. We are gonna fight. You know, for Fight. Fight. For people who don't know, when Marshall and I first started co hosting together, we had this whole list of recurring segments we wanted to have. And one of them that we came up with was called fight me or let's fight. Let's fight fight. Yeah. Or was it fighting? Maybe it was fighting. Yeah. I think it it was fighting me. I think it might've been fighting me. Yeah. And the idea was we're gonna figure out stuff we disagree on and we're gonna debate it on the podcast. Uh-huh. Well, here's the problem, Marshall. You and I don't disagree on that much stuff. Yeah. Not very often. Yeah. And so today, we found something we can actually fight about. So we're gonna fight in today's episode, but, of course, we gotta give a shout out to Catch. Catch asks, you, listener, why did you become a freelancer? Was it for freedom or flexibility? Well, probably was not because you wanted to manage your own health insurance, taxes, and retirement. CATCH does all that for you. They offer benefits and personal payroll for the self employed. So make sure you're covered. You're well into 2023, all you freelancers out there. Make sure you're covered and protected, getting the best benefits you can at catch.co/designdetails/health, or just tap the link in the show notes. Once again, that's catch.co/designdetails/health. Thank you, Catch. Thanks, Catch. We also have some new very important pixel this week. Welcome to the fam. Martina Nikolaova, Marchin witchery. Hey, Marchin. Welcome. Oh, Marchin. Nice. Uh-huh. I think I think Marchin wanted to hear the bonus interview final cut. He'll be gone next month. That's our that's our big scam as we just have guests on the podcast and tell them something juicy dropped in the sidebar, and then they have to subscribe. So thanks, Marchin. Alright. Shout out to Kathy Ma, not my full name, Justin Frank, Adam Simon, Jason Reynolds, Daniel McGill, Tongtong Liu, and Kieran Boswell. Hey. What a list. Welcome to the hot tub, everybody. Welcome welcome on in. If you didn't know, we are a listener support podcast. All the people that we just mentioned are supporting us on Patreon at patreon.com/designdetails. Over there, we publish bonus content. When we, you know, drop this main episode, We also drop some bonus content for our Patreon supporters, and it only costs a dollar a month. …
Get the full transcript (6,155 words) + summary by email — free
One-time email with the complete transcript and AI summary of this episode. No account needed.
One email, no spam. We’ll also show you what SignalCast does.
You just read a 3-minute summary of a 29-minute episode.
Get Design Details summarized like this every Monday — plus up to 2 more podcasts, free.
Pick Your Podcasts — FreeKeep Reading
Books, tools, and gear mentioned in this episode
SignalCast may earn commission on purchases via these links.
Tools
by Figma
“FigJam's lack of a layers panel demonstrates how freeform tools intentionally avoid structural constraints during brainstorming.”
by Figma
“Brian Lovin and Marshall Bock debate whether designers should name their layers in Figma files.”
“Modern CSS frameworks like Tailwind use utility classes instead of semantic naming, reducing the importance of layer names in code translation.”
“Diagram and similar tools are developing AI layer naming to automate this process, suggesting computers may eventually handle naming hygiene automatically.”
company
“When building component libraries like YouTube's design system, layer names directly impact usability for other designers.”
More from Design Details
We summarize every new episode. Want them in your inbox?
Similar Episodes
Related episodes from other podcasts
Pod Save America
Nov 23
What Will Democratic Governance Look Like? + Lina Khan (Crooked Con)
The AI Breakdown
Aug 17
AI Companies Still Haven’t Delivered on Their Biggest Promises
Modern Wisdom
Aug 17
AI DEBATE: What Will the World Actually Look Like in 2040? - #1138
All-In with Chamath, Jason, Sacks & Friedberg
Jul 24
The Fight Over Open Source AI, Anthropic's $1.5B Payout, NYC Socialists: Evictions = Violence?
All-In with Chamath, Jason, Sacks & Friedberg
Jul 11
More Trillion Dollar IPOs, Anthropic $3T, Zuck's Price War, China Ends Open Source?, Trump Accounts
Explore Related Topics
This podcast is featured in Best Product Management Podcasts (2026) — ranked and reviewed with AI summaries.
Read this week's AI & Machine Learning Podcast Insights — cross-podcast analysis updated weekly.
You're clearly into Design Details.
Every Monday, we deliver AI summaries of the latest episodes from Design Details and 192+ other podcasts. Free for one show.
Start My Monday DigestNo credit card · Unsubscribe anytime