I was balding while trying to make my site look good. This is my story.
The Setup
I've rebuilt IndianCoffeeBeans.com enough times to qualify for a coffee-funded pension.
This time, I was doing it right. Fresh Next.js 15. React 19. Tailwind 4. Confidence: 10/10.
npm install tailwindcss shadcn ui lucide clsx supabase react-query zod zustand ..
Dropped in layout, added ShadCN, wired up my containers… hit reload. What did I get?
Enter GPT, Claude, Windsurf… and Panic
Like any solo dev spiraling into CSS madness, I called in the AI Avengers:
- GPT said: "edit
tailwind.config.ts" - Claude said: "try
tailwind.config.jsinstead" - Windsurf hallucinated entire working projects that didn't actually run
I even tried "multi-chat prompts" in Windsurf to keep context between chats. It felt like holding a team meeting with three confused interns.
Meanwhile, I was 7 configs deep and the only thing rendering was my despair.
YouTube + Taskmaster (UK) = Accidental Breakthrough
Somewhere between rage-watching Taskmaster and doom-searching "tailwind 4 layout not working", I stumbled onto themecn.dev.
Fifteen minutes later: Fonts rendering · Layout styled · Dark mode working · No more screaming into the abyss
The Part I Should've Started With
Eventually… I gave up trying to be clever. I pasted the Tailwind 4 release blog directly into Claude like a desperate high-schooler cheating on an open-book test.
And there it was:
"Tailwind 4 reads design tokens from your CSS layer, not your config."
Translation: Every single thing I tweaked in tailwind.config.ts? Tailwind didn't even care. Like yelling into a void. With prettier formatting.
TL;DR (aka future GT, read this first next time)
- Tailwind 4 doesn't need
tailwind.configif you're using design tokens globals.cssis the new single source of styling truth- themecn.dev will save your soul in 15 minutes
- GPT and Claude can't debug CSS hallucinations
- ShadCN only looks good after you beat the tokens into shape
- Yes, I downgraded to Tailwind 3.14.
- Yes, I upgraded back.
- No, I don't want to talk about it.
Lesson learned: Don't fight the framework. Don't fight the LLMs. Just read the damn docs. Or at least feed them to your AI therapist first.
Coming soon: "The Server Action Bug That Almost Killed My SEO" — Spoiler: It involved a misplaced 'use server' and a very bitter brew.