Large projects need boundaries
As a project grows, class composition should be organized around components, not pages full of repeated markup. Keep reusable components in a shared UI layer and domain-specific components close to their feature.
Centralize tokens
Keep theme variables, custom variants and global CSS entry points in a predictable location. Avoid scattering design-token definitions across many files.
Review utility complexity
Very long class strings can be legitimate for complex components, but repeated long strings often indicate a missing component abstraction or token.
ADVERTISEMENT