What problem does it solve?
It prevents broken theming and inconsistent UI styling caused by hardcoded Tailwind colors, inline styles, and incorrect Tailwind v4 setup that won’t adapt correctly in dark mode.
Core Features & Use Cases
- Tailwind v4-safe utility writing using the correct AstroDeck approach (CSS-driven tokens, no tailwind.config.mjs).
- Token-first color usage via CSS variables registered through the @theme directive so primary/foreground colors remain consistent.
- Dark mode done correctly by using semantic tokens (e.g., bg-background text-foreground) instead of relying on dark: utility prefixes.
- Anti-pattern detection guidance to catch hardcoded color utilities and style="..." usage (based on the repository learnings).
Quick Start
Use the tailwind skill whenever you are reviewing or editing class names or global styling so any colors and layout styles remain token-driven, OKLCH-based, and compatible with Tailwind v4 dark mode.