The system you have is the system you have. Observe it, model it, and accept it for what it is. Do not be tempted to make the system beautiful for beauty's sake.
Tokens encode values, contexts encode decisions
When you need a foreground colour, there should be only one token you reach for in a given situation. All other considerations are encoded in contexts, whether that be state, theme, sentiment, mode...
Don't show your (all) working
Keep a small public surface of tokens for consumption. Exactly how those tokens resolve to a final value are an implementation detail. Keeping this private keeps the system limber.
ONE = 1 is an antipattern (mostly)
Token values must be able to be changed without changing the name of the token. The only possible exception to this is to 'enforce' quantisation, though there are often better solutions.
Names from usage, not origin
Tokens should be named based on their usage. Start at the usage token and work backwards from there, adding generalisations, rather than starting from definitions and adding specificity.