Last time I was leaving front end there were rumors of css coverage tools. That would certainly be a start.

It's a thing in Chrome Dev Tools now: https://developer.chrome.com/docs/devtools/coverage/

now, if only it could persist the data while navigating to other pages, it would be a lot more useful

This I remember now. So that still hasn’t been sorted out? Pity.

and also automate all possible interaction for styles applied only in certain condition for that page?

CSS is Turing complete, although you could probably handle 99.9% of real world cases without dealing with that.

This sort of does that I think, but it more just dedupes it rather than just identifying the duplicates. But I agree that like some tooling to make CSS more human readable, and like to tame unwieldy enlarged CSS and subdue it to the useful and the good and the organized that would be a very useful thing, but I couldn’t find anything… besides this haha! :)

Yeah, in a related anecdote it’s surprising how sparse the landscape of CSS tools seemed at least for command line tools that I was looking for.

I didn’t want an ID plug-in because I didn’t really use anything except for vim and I don’t really use plug-ins for that.

That might be kind of a niche set up but when I went looking for like even just something to sort the properties by some standard order within each rule, I couldn’t find anything current that worked in my searching anyway.