Tailwind CSS interview question · Most asked
How do you avoid repeating long class lists?
Summary
Extract components (React, Vue, Blade, partials) or loops so each pattern is written once. Use @apply sparingly for small global cases such as third-party HTML. Use @utility for custom utilities that work with variants. Avoid rebuilding a component framework with @apply.
Longer Answer
Multi-cursor editing and good class sorting help too; the official Prettier plugin sorts classes consistently.
Key Points
- Components and loops first.
- @apply sparingly.
- @utility for custom utilities.
- Prettier plugin for order.
Deep dive: Tailwind CSS Tutorial: Reusing Styles
Explanation
What interviewers look for
Prefers components over @apply.
More most-asked Tailwind CSS questions
- Why doesn't className={`bg-${color}-500`} work, and what should you do instead?
- How do you customize Tailwind's design tokens in v4?
- Explain Tailwind's responsive design approach.
- How does Tailwind decide which CSS to generate?
- What is Tailwind CSS and what does 'utility-first' mean?
- What changed in Tailwind CSS v4 compared with v3?
- How do you make Tailwind interfaces accessible?
- What's the difference between flex and grid in Tailwind, and when do you use each?