Atomic CSS
acss.io
acss.io
I would rather see tools that attempt to solve hyperspecific probems (e.g. culling unused styles, visualizing namespace collisions) without disturbing existing best practices (e.g. modular CSS, BEM, using preprocessors like SCSS and post-processors like PostCSS).
I didn't care for it eight months ago, either. Non-semantic solution in search of a problem. I understand the motivation, I'm just not convinced this is "better".
I thought BEM and other css frameworks/conventions solved this problem.
For example:
myComponent/myComponent.jsx
myComponent/myComponent.css
in myComponent.css .myComponent {
/* whatever */
}
Since all of your components are uniquely named(I hope), you can just use flat single class selectors without any specificity issues.