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.
91
88%
Does it follow best practices?
Impact
97%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Tailwind v3 to v4 migration
CSS @import syntax
100%
100%
No @tailwind directives
100%
100%
@theme for custom colours
100%
100%
Custom font in @theme
100%
100%
No tailwind.config.js corePlugins
100%
100%
No deprecated opacity utilities
100%
100%
Opacity replaced correctly
100%
100%
No deprecated flex-grow/shrink classes
100%
100%
flex-grow replaced correctly
100%
100%
Gap over margin spacing
0%
0%
Dark mode and gap utilities in new component
Dark mode on card bg
100%
100%
Dark mode on text
100%
100%
Dark mode on section
100%
100%
Gap for sibling spacing
100%
100%
No margin-based sibling spacing
100%
100%
Responsive grid
100%
100%
No deprecated opacity classes
100%
100%
No deprecated flex utilities
100%
100%
Consistent border/rounded style
100%
100%
Dark mode border
100%
100%
Fresh Tailwind v4 setup with custom theme
v4 @import syntax
100%
100%
No @tailwind directives
100%
100%
@theme for brand colour
100%
100%
No tailwind.config.js
100%
100%
Responsive grid breakpoints
100%
100%
Gap for grid spacing
100%
100%
Dark mode background
100%
100%
Dark mode text
100%
100%
No deprecated opacity utilities
100%
100%
No deprecated flex utilities
100%
100%
Brand colour applied to CTA
100%
100%
9c28875
Table of Contents
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.