I feel like this is akin to &quot;killing the patient to cure the disease.&quot; In the uses I can see for this, the way this framework solves the problem, to me, seems to be worse than any problem itself. Namely, I would like to know how this is any better than !important on your CSS properties.<p>Firstly, you&#x27;re messing up your separation of concerns, you&#x27;re also messing up an attribute with values that other developers will probably see as a bug — &quot;why isn&#x27;t this in a style tag?&quot; It also won&#x27;t work with JavaScript disabled (a few people will complain about that, they always do).<p>Why use classes at all? If the idea is to not rely on CSS, we could  use a data attribute, like data-mimic or data-mimic-width=&quot;1&quot;, to apply to additional styles (although some CMS&#x27; will struggle with this).<p>(I realise its so easy to be negative, and HN submissions usually have their unfair share of criticism from people who think they know better. Although it obviously solves a problem for the author, at the crux of it, I&#x27;d refactor this if I found it in any projects I look after.)