Elven Maps - Naming That Survives Migrations

An old elven map still guides travelers because the names point to meaning, not fashion. Winter Pass is still Winter Pass, even after borders and banners change. Your product needs names like that so redesigns and tool moves do not turn into wilderness.

To keep your map timeless, follow these naming rules

• 🎯 Tokens - prefer purpose: [action.primary], [surface.muted], [text.danger], not [blue-500] or [lightGrey].

• 🧱 Levels - keep three layers: core decisions, semantic meaning, component usage. Core holds raw values, semantic describes intent, component ties usage: [button.padding.md].

• 🗺️ Flows - name routes and steps: [Flow.SignUp.Happy] , [Flow.SignUp.Recovery].
Inside: [Node.EmailEntry], [Node.OTPVerify],
and edges with clear verbs: [submit], [cancel], [error].

Quick checks that keep the map readable
• Swap test, can you rebrand without renaming intent, if not, the name is cosmetic.
• Review test, can a new teammate predict behavior from the name alone, if not, add clarity.
• Drift test, keep a one page naming charter and glossary, define what “primary” means, where aliases live, and how states are written.

Tiny example:
Rename [BlueButton] to [ButtonPrimary] and connect it to [action.primary]. When marketing pivots the palette, your logic and prototypes still make sense, links still work, reviews stay about outcomes, not color codes.

Keep your names timeless and the path will stay clear, even when the scenery changes.