I think we largely agree, so I'll go back to focusing on the tool. > Isn't that something Tailwind can't do? Tailwind will load every style, every time, right?

I think we largely agree, so I'll go back to focusing on the tool. > Isn't that something Tailwind can't do? Tailwind will load every style, every time, right? Tailwind's only function is: - Scan codebase - Generate classes - Save them in a file with the a .css extension. Anything else that you want is outside the scope of the tool. It makes no assumptions about what your files are named, where they are, or how it's loaded in the browser. At the end of the day, it's up to the developer to write `<link rel="stylesheet" href="/path/to/my/generated/file.css">` This is no different or made easier/harder by using Tailwind.