This is your first stop when Tailwind classes aren't showing up in the browser or your v3 to v4 migration breaks. It walks through the usual suspects: dynamic class concatenation that JIT can't detect, PostCSS plugin configuration for v4 (it's @tailwindcss/postcss now, not the old setup), content path issues, and specificity conflicts. The debugging checklist is solid for narrowing down whether it's a build problem, a cache problem, or you're just concatenating strings wrong. Honestly most Tailwind debugging comes down to "stop doing `text-${color}-500`" but this covers the less obvious stuff too, like why IntelliSense stopped working or why your production build is missing half your styles.
npx skills add https://github.com/josiahsiegel/claude-plugin-marketplace --skill tailwindcss-debugging