Debugging missing Tailwind classes

Common causes

Missing styles often come from dynamic class construction, an unscanned source directory, a typo in the utility, a build pipeline issue or a component file outside the detected sources.

Debug systematically

First test the utility with a literal class in a known scanned HTML/component file. If it works, the problem is probably class detection or runtime composition rather than Tailwind itself.

Check generated CSS

Inspect the compiled CSS to determine whether the utility was generated. This separates generation problems from browser, cascade or component problems.