Tailwind CSS Best Practices Core Principles - Prefer utility classes over custom CSS for most styling - Keep class lists readable by grouping: layout → spacing → typography → color → effects - Use semantic HTML first; utilities should enhance, not replace structure Variants & State - Use , , , , and variants where appropriate - Prefer and variants for stateful styling tied to DOM semantics - Use and for parent/sibling state without extra JS Responsive & Container Queries - Start with the base styles, then add responsive variants ( , , , ...) - Use container query utilities when layout depends…