tailwind-css

Topics in the source

• Tailwind CSS
• Routing
• Completion

Follow the installed Tailwind version and the repository's tokens, components, class-merging utility, CSS entrypoint, and nearby UI. They take precedence over this skill. Do not add packages, change integration, or migrate versions without a request and local need. Apply coding preferences only where the project is silent. For v4 configuration, migration, directives, or generated classes, use v4 rules and the matching official docs. Read tailwind-variants, tw-animate-css, or ESLint only when that integration exists locally or the request adds it. Do not apply v4 syntax to an older installation. Preserve responsive, interaction, accessible, and dark-mode behavior. Do not redesign beyond the request. Define the intended visual and state change. Reuse local conventions. Keep classes statically discoverable. If source registration or generated mappings change, run the real Tailwind build and confirm the expected utilities. Run required repository checks and inspect the changed states at one representative viewport for a small style edit. Broaden to narrow/wide viewports, themes, and interactions when responsive rules or shared styling changed. When markup is transformed by JavaScript o

This is an excerpt. Refer to the complete source and its current requirements.