Object First Naming

Object first naming is the practice of labeling icons by the physical or digital object they show instead of the action they trigger or the idea they stand for. The magnifying glass is search. The trash can is trash. The left pointing arrow is arrow-left. Objects are stable. Contexts change. A single name that describes the shape survives product pivots team changes and feature bloat that would destroy a metaphor based system. This rule forms half the governance layer that keeps an icon library coherent past 50 symbols. Every icon system needs discoverability as much as it needs optical balance. Without object first naming even the most beautiful set becomes unusable. Designers waste hours hunting for the right asset or worse they create duplicates because the existing one was named using last quarters product language. The rule forces everyone to speak the same visual vocabulary.

What it is not is naming by metaphor or by desired user behavior. Calling the pencil edit or the eye view or the star favorite guarantees collisions. One designer uses star for bookmark. Another uses it for rate. A third uses it for important. You end up with three stars each with a different name and none discoverable. It is not using cute brand terms that only the original designer understands. It is not ignoring consistent formatting like kebab case or required suffixes for direction and variant. It is also not a suggestion. It is a hard rule enforced at contribution time. The moment you let one icon slip through named by metaphor the entire system starts to decay. We have audited libraries at scaleups that went from 60 icons to 240 in two years purely because naming was left to personal preference.

Concrete example. Shopify Polaris switched to object first naming in 2022 after their icon set had fragmented across seven different product teams. The icon showing a delivery truck is now delivery-truck not ship or fulfill or logistics. The synonym map redirects searches for those terms back to the canonical name. When they launched Shopify Magic in 2024 the AI team needed an icon for generate. They did not add a new magic-wand icon with a metaphor name. They used the existing sparkles icon and updated the map. The entire admin suite stayed visually coherent even as the product added dozens of new surfaces. Engineers import Icon name=delivery-truck with confidence that the asset matches the Figma library exactly.

A second example is the open source library Lucide. Every one of its 1100 plus icons follows object first. No icon is named submit or approve or toggle. They are named paper-plane check-circle and toggle-left. When Linear adopted Lucide as their base in 2023 they added only 14 custom icons for concepts unique to issue tracking. Because both libraries spoke the same naming language the integration took hours not weeks. No renaming layer. No duplicate SVGs. Their synonym map now contains over 600 terms so a designer searching for todo task or checklist lands on the same check-square icon every time. Vercel followed the same pattern in 2025 when expanding their dashboard. The copy icon stayed copy not duplicate or clone. The synonym map handled every creative search term so the library never bloated.

When to use object first naming deploy it the day your team grows beyond a single designer or when your icon count crosses 40. Use it for any product UI library that must survive multiple years and multiple hands. Use it alongside the full contribution process that demands a search first step a justification sentence optical review and synonym map updates. Use it when you want engineers to trust and actually use the component library instead of exporting random SVGs from random icon sites on a deadline. Pair it with kebab-case for every multi-word name and variant suffixes like search-filled or arrow-right-duotone so the names stay grep-able in codebases.

Avoid it for marketing illustrations that change every campaign. Avoid it in experimental phases where you are still validating which icons the product needs. Avoid it if your brand voice deliberately plays with visual metaphors as the primary form of delight like some consumer social apps do. In those narrow cases metaphor names can create personality. Everywhere else they create technical debt that compounds quarterly.

The difference between a system that lasts and one that collapses is rarely the grid or the stroke weight. It is almost always whether the names let humans and computers find the right asset before they decide to redraw it wrong. Name the object not the metaphor or watch your icon library turn into expensive decoration.