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.
82
95%
Does it follow best practices?
Impact
100%
1.00xAverage score across 1 eval scenario
Passed
No findings from the security scan
Tailwind v3 to v4 migration
v4 import syntax
100%
100%
No @tailwind directives
100%
100%
@theme brand color
100%
100%
No corePlugins
100%
100%
flex-shrink replaced
100%
100%
flex-grow replaced
100%
100%
bg-opacity replaced
100%
100%
text-opacity replaced
100%
100%
overflow-ellipsis replaced
100%
100%
decoration-clone replaced
100%
100%
5b33d49
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.