Consensus on building components that are shared across projects?

[erickreutz]

Hi! Using tailwind and loving it. I had a general question though that I can't seem to find a straight answer to. I'm wondering if there is a general consensus on how to build components that are shared across projects that have potentially different styles and themes? It's my understanding that if I build a component with a certain tailwind config and then import that component into a project that could potentially have a different tailwind config - the styles would not work as originally intended on the imported component and things would clash unintentionally.

Is using prefix the suggested way to solve this? Using @apply to modulize component styles with traditional BEM like
class names? Make all the shared components headless?

I'd like to build some components using tailwind and re-use them across projects that have different styles. What is the preferred approach here?