But most of the time, designers don't know how to stick with a standardized padding and margin, so I find that without exception, an org requires me to develop "cryptic" representations of margin and padding, such as mr1 (margin right to 1 degree, or 5 px) or pl2 (padding left to 2 degrees, or 10px).
I've also rolled entirely new features without writing a single line of CSS. This is a way to mitigate CSS bloat. I take it you've never actually tried to deal with the problem of CSS bloat, or you'd find either 1) you'd have to hold a gun to designers' heads or 2) do exactly what I just showed you.
Usually a quick follow-up question will reveal the mistake and the designer is happy to make the correction.
This has been my best weapon against CSS bloat.
* Components and patterns are standardized, allowing for less process in design reviews and quicker iteration
* Engineers can create component libraries that mirror style guide elements and turn frontend work into something a little closer to 'lego' building