Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex/grid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3/v4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML/CSS component, CSS file audits, build tool configuration, and vanilla CSS.
90
97%
Does it follow best practices?
Impact
98%
0.98x2 of 3 eval scenarios. Add 1 more for a full score.
Passed
No findings from the security scan
Use search-docs for detailed Tailwind CSS v4 patterns and documentation.
corePlugins is not supported in Tailwind v4.In Tailwind v4, you configure Tailwind in CSS with the @theme directive. You don't need a separate tailwind.config.js file:
@theme {
--color-brand: oklch(0.72 0.11 178);
}In Tailwind v4, import Tailwind with a regular CSS @import statement instead of the @tailwind directives used in v3:
- @tailwind base;
- @tailwind components;
- @tailwind utilities;
+ @import "tailwindcss";Tailwind v4 removed deprecated utilities. Use the replacements shown below. For opacity, drop the *-opacity-* class and append the value as a modifier on the existing color: bg-blue-500 bg-opacity-50 becomes bg-blue-500/50, text-white text-opacity-75 becomes text-white/75.
| Deprecated | Replacement |
|---|---|
| bg-opacity-* | bg-{color}/* |
| text-opacity-* | text-{color}/* |
| border-opacity-* | border-{color}/* |
| divide-opacity-* | divide-{color}/* |
| ring-opacity-* | ring-{color}/* |
| placeholder-opacity-* | placeholder-{color}/* |
| flex-shrink-* | shrink-* |
| flex-grow-* | grow-* |
| overflow-ellipsis | text-ellipsis |
| decoration-slice | box-decoration-slice |
| decoration-clone | box-decoration-clone |
Use gap utilities instead of margins for spacing between siblings:
<div class="flex gap-8">
<div>Item 1</div>
<div>Item 2</div>
</div>If existing pages and components support dark mode, new pages and components must support it the same way, typically using the dark: variant:
<div class="bg-white dark:bg-gray-900 text-gray-900 dark:text-white">
Content adapts to color scheme
</div>bg-opacity-* and flex-shrink-*@tailwind directives instead of @import "tailwindcss"tailwind.config.js instead of the CSS @theme directivelaravel/boost
30e24b7
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.