I agree. First of all, why is a ui class necessary? Second, what's large? The icon, the button, the label? All of it? What's red, the icon or the button? Certainly not both. There's a reason we have classes like "btn btn-small icon-* icon-2x". A large icon in a small button. I think those names are more 'semantic'.

I assume the ui class is there for namespacing, which I think is a good idea.

I don't see any content; those are all stylistic properties.

Yeah that one was too specific for my liking I don't think you should use colors names like 'red' as a class. What if you decide you don't want it to be red?

Remove the "red" class from the element?

I used to eschew any and all presentational classes, but it makes development quicker for me to use them occasionally, esp with css frameworks.

I guess my point was you'd have to refactor your html and css as well as the property itself

Use a SASS mixin instead? @include red;