Case against the modularization of CSS: Cargo Cult CSS:
Selectors should communicate useful information to developers. The purpose is the same but a contextual selector is far more informative to the developer than a class selector, as it communicates context. It’s a lot easier to understand the purpose behind a rule if the selector tells you that it only applies to elements within a certain scope.
Must admit that I still have to contain myself selector-wise — I used to write heavy selectors back in the day — when applying concepts like SMACCS (which in fact has changed how I write CSS nowadays), as some of the stuff such as
<article class="news news-breaking"> can be achieved by using a preprocessor (here
I guess the solution can be found somewhere in between, although my solution might not even be your solution. As Jeremy Keith once put it: it depends.
In favor of the modularization of CSS, be sure to read CSS Architecture.
The bottom line is that whatever you do to organize your code, make sure you judge your methods by whether or not they actually help make your development easier and more maintainable in the long term.