Issue Check

• I have checked existing Issues and I feel this feature request has not been raised

Is your feature request related to a problem?

Blowfish supports assets/css/custom.css as a user override loaded after the theme styles, but this file is only minified and not processed by the Tailwind build pipeline.
As a result, Tailwind directives such as @apply cannot be used in custom.css, which prevents users from defining reusable Tailwind-based classes and using them alongside native Tailwind utilities in layout templates.

Describe the solution you'd like

Allow assets/css/custom.css (or a documented user CSS entry file) to be processed by the same Tailwind pipeline as the theme’s CSS.
This would enable users to define custom classes using @apply and reuse them in layouts/*.html as first-class Tailwind extensions, without setting up a separate Tailwind instance.

Describe the alternatives you've considered

• Running a separate Tailwind setup in the site project (works, but duplicates tooling and can diverge from the theme’s Tailwind config).
• Writing plain CSS without @apply (works, but removes Tailwind composition and reuse benefits).

Additional context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct