I will assume you know what a design token is and why it might be smart to implement. (Otherwise. There is plenty of great articles and talks on the subject)

Naming structure

In order to name your tokens consistent you will need a structure. Instead rewriting what Nathan Curtis have written so well I will just recommend you to read his article a couple of times about different naming structures. Naming Tokens in Design system — by Nathan Curtis

We, the Anchor design team, didn’t locate the the perfect naming structure for design tokens during our research. We identified the important thing was to do what made sense for our system and our stakeholder.For Trygs Design System Anchor we ended landed on this:We ended up with 11 steps to consider when naming a token. It is a lot and time will tell if it was too much – but this was the amount we needed to feel covered.One thing was clear. It was not enough to have just a structure. We needed to document what each step could contain. So we (or somebody else) could name consistent after 2 weeks, 3 months. So we needed to document.