Rules Hub
Code Ruleset
Rule priority, scope & exceptions
Use this to align rules with the senior-level structure (P0/P1/P2, scope, exceptions/tradeoffs).
Do not create a shared file re-exporting Tailwind base directives
Configure Tailwind entry points for the installed version and loaded bundles so base/reset output is not duplicated unintentionally.
Bad example
| 1 | /* use-tailwind.css imported by many entries */ |
| 2 | @tailwind base; |
| 3 | @tailwind components; |
| 4 | @tailwind utilities; |
Explanation (EN)
A shared entry strategy that accidentally emits the reset multiple times changes output size and cascade.
Objašnjenje (HR)
Good example
| 1 | /* Tailwind v4: the application's single loaded base stylesheet */ |
| 2 | @import "tailwindcss"; |
Explanation (EN)
This example uses one application entry; independent bundles need a separately verified strategy.
Objašnjenje (HR)
Notes (EN)
Inspect which CSS entry points are built and loaded together, then ensure framework reset/base output is emitted only where the installed Tailwind version and bundle strategy require it.
Exceptions / Tradeoffs (EN)
Independent bundles may need their own entry setup. Tailwind v3 directives and v4 imports differ; repeating base directives in every co-loaded entry can duplicate resets.