AI summary by TwinMind
I WISH I Knew These Tailwind Tips Earlier
Theo - t3․gg
9m 14s
Cheat Sheets for Learning Tailwind
- Use cheat sheets to quickly translate CSS knowledge to Tailwind classes
- Docs focus on what/where/why, not which specific class to use
- Find padding class, flex-grow class quickly via one-page reference
- Google "Tailwind cheat sheet" for good options
- Helps learn Tailwind much faster, especially for CSS-experienced developers
Keep It Simple - Don't Fear Copy-Paste
- Tailwind doesn't prescribe specific architecture patterns like styled-components/CSS modules
- Simple approach: copy-paste class names rather than over-abstracting
- Example: navbar with 4 identical links - copy class names 4 times vs creating component
- Use VS Code multi-cursor (Command+D) to change multiple instances simultaneously
- Tailwind team recommends this approach in "Reusing Styles" docs
- "Use editor and language features like multi-cursor editing"
- "You'd be surprised how often this ends up being the best solution"
- No benefit to additional abstractions if can edit duplicated class lists simultaneously
- Alternative approaches when needed:
- Use loops for repeated elements
- Abstract into components for more complex reuse
Avoid @apply Directive
- @apply lets you use Tailwind classes inside CSS files
- Creates bad abstraction, throws away Tailwind's biggest benefits
- Causes high chance of technical issues
- Adam Wathan (Tailwind creator) "lightly regrets adding @apply"
- Feature causes most issues for Tailwind team
- Estimated cost: hundreds of thousands of dollars in debugging time
- Only acceptable use: applying Tailwind colors to body background
Tailwind Prettier Auto-Sorting Plugin
- "Most important thing to have as part of Tailwind experience"
- "You're not really using Tailwind if you're not using this"
- Three critical benefits:
- Conflicting classes detection: Conflicting classes appear nearby, easier to debug
- Code review efficiency: Consistent order makes properties predictable (padding, flex, display always in same position)
- CSS specificity consistency: Class order matches CSS stylesheet order
- CSS class application based on stylesheet order, not HTML class name order
- Example:
<div class="a b">vs<div class="b a">- both render identically based on CSS order - Mismatched orders between HTML and CSS create debugging nightmares
- Different load times in production/dev can cause issues
- Example:
- Auto-sorting ensures HTML class order matches CSS order, preventing specificity bugs
Embrace Copy-Paste Philosophy
- Don't default to npm install/abstraction for every feature
- Tailwind goal: make writing styles fast, simple, reliable
- Copy-paste from Tailwind UI, other sites, own codebase without guilt
- Tailwind classes consistent across all projects
- Easy to move markup between different projects
- No issues when dropping code into new project
- Valuable for:
- Developers working on multiple projects
- Companies with multiple codebases
- Context switching between teams
- Code reuse without shared component libraries/monorepos
- Tailwind syntax acts as contract - honored consistently across projects
Tailwind Config Best Practices
- Use config to add things, not change things
- Don't try to make Tailwind work like styled-components or other systems
- Avoid going "crazy with the Tailwind config"
