--- name: tailwindcss-development description: "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." license: MIT metadata: author: laravel --- # Tailwind CSS Development ## Documentation Use `search-docs` for detailed Tailwind CSS v3 patterns and documentation. ## Basic Usage - Use Tailwind CSS classes to style HTML. Check and follow existing Tailwind conventions in the project before introducing new patterns. - Offer to extract repeated patterns into components that match the project's conventions (e.g., Blade, JSX, Vue). - Consider class placement, order, priority, and defaults. Remove redundant classes, add classes to parent or child elements carefully to reduce repetition, and group elements logically. ## Tailwind CSS v3 Specifics - Always use Tailwind CSS v3 and verify you're using only classes it supports. - Configuration is done in the `tailwind.config.js` file. - Import using `@tailwind` directives: ```css @tailwind base; @tailwind components; @tailwind utilities; ``` ## Spacing When listing items, use gap utilities for spacing; don't use margins. ```html
Item 1
Item 2
``` ## Dark Mode If existing pages and components support dark mode, new pages and components must support it the same way, typically using the `dark:` variant: ```html
Content adapts to color scheme
``` ## Common Patterns ### Flexbox Layout ```html
Left content
Right content
``` ### Grid Layout ```html
Card 1
Card 2
Card 3
``` ## Verification 1. Check browser for visual rendering 2. Test responsive breakpoints 3. Verify dark mode if project uses it ## Common Pitfalls - Using margins for spacing between siblings instead of gap utilities - Forgetting to add dark mode variants when the project uses dark mode - Not checking existing project conventions before adding new utilities - Overusing inline styles when Tailwind classes would suffice