The real cost of ignoring CSS architecture
Most teams know this matters. Fewer have decided who owns it. Nobody bills you for neglecting CSS architecture. The cost shows up somewhere else.
The question is rarely whether something can be built, but what it costs to keep running afterwards. Assume whoever inherits this will have half your context and none of your patience.
Where the cost lands
- Time spent on work that should not have been necessary
- Enquiries that quietly never arrive
- Naming conventions prevent the specificity arms race
- Rework, once the problem is finally visible
Custom properties centralise the values you change most. The cost of getting this wrong is rarely visible on the day it happens. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.
Where to go from here
Deleting CSS should be as easy as adding it. Getting it slightly wrong is survivable. Ignoring it entirely is not. Budget a little time for it every quarter and it never becomes a project of its own.
How to tell if yours is fine
Most development decisions are really maintenance decisions wearing a different hat. Three things worth confirming about CSS architecture before you move on:
- Someone can say what the current setup is without going to look
- Naming conventions prevent the specificity arms race — and you know whether that is true here
- There is a way to tell whether the last change to this helped
If you want a second opinion on how yours is set up, ask.