Except you should be learning a "language" anyway because that's what building a product is about. To use your "rounded" thing as an example: Design systems s

Except you should be learning a "language" anyway because that's what building a product is about. To use your "rounded" thing as an example: Design systems should have their own definitions of what a "rounded" thing is. The designs also probably have different types of border-radius based on if it's a container element, or a button, or a pill button, etc. So you define those as different types of "rounded". Small, medium, large. Round, rounder, roundest. They could be whatever you want. This way, your team doesn't have to remember that 10px = round, designers or PMs just say "round" and you use the "round" utility class. Or if they don't like styling they can say "hmm what about 'rounder'?" and you use the rounder class. That's what Tailwind aims to solve is to 1) define a common language across the team and 2) make that easily available for the FE dev to implement versus trying to cross-reference what "round" is.