> The "just write a component" strategy is really bad if you're trying to reuse your CSS across different projects and frameworks. I just want my buttons and ca

> The "just write a component" strategy is really bad if you're trying to reuse your CSS across different projects and frameworks. I just want my buttons and cards and components to LOOK the same, not function the same. Could you explain the problem more? There's lots of Tailwind based component systems that have reusable button and card components you could look at for ideas how to structure this. In comparison, reusing traditional CSS is usually a nightmare because the CSS for a single component is usually spread across multiple files and difficult to disentangle. That's part of the problem Tailwind tries to solve.