When do you break Tailwind's utility-first approach for complex components?

[alex-x-x-x-x]

I'm working on a large TailwindCSS project using React and I'm thinking about long-term maintainability. Tailwind works great for most components, but for some of the more complex UI elements, I'm debating between utility classes and separate CSS files.

For those with production Tailwind apps: what's your approach for deciding when to keep something in utility classes versus breaking it out into separate CSS? I'm not struggling with implementation, but I just want to make sure I'm setting up for good maintainability.

Has your approach to this changed as your projects grew? Any lessons learned about what makes for a more maintainable codebase when working with complex UI components in Tailwind?

Thanks for your help and time.