Tailwind Best Practices

by asyrafhussin1aa0ff717c10MIT86 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 6 weeks ago

Tailwind CSS patterns and conventions. Use when writing responsive designs, implementing dark mode, creating reusable component styles, configuring Tailwind, or migrating from v3 to v4. Triggers on tasks involving Tailwind classes, responsive design, dark mode, CSS styling, or "migrate to Tailwind v4".

Instructions onlySoftware Development
AI-generated overview

Provides Tailwind CSS v3.4 and v4 patterns for responsive design, dark mode, components, config, and migration.

What it does
This instruction-only skill supplies 29 rules covering responsive layouts, dark mode, reusable component styles, theme configuration, and v3-to-v4 migration. It first detects the installed Tailwind version from package.json or CSS signals, then directs the agent to the matching rule files. It produces guidance and code patterns rather than files or scripts.
When to use it
Use it when writing Tailwind CSS layouts, implementing dark mode, building reusable component styles, configuring Tailwind, or migrating a project from v3 to v4. It is intended for styling work in projects that already use Tailwind CSS.
Requirements
No scripts or packages are required beyond the agent; the skill is documentation only. It references project files such as package.json and CSS entry files for version detection, and mentions optional ecosystem tools like clsx, tailwind-merge, and CVA.

Tailwind CSS Best Practices

Comprehensive patterns for building consistent, maintainable interfaces with Tailwind CSS v3.4+ and v4. Contains 29 rules covering responsive design, dark mode, component patterns, configuration, and v4 migration.

Metadata

  • Version: 1.0.0
  • Framework: Tailwind CSS v3.4+ / v4.0+
  • Rule Count: 29 rules across 8 categories
  • License: MIT
  • Documentation: tailwindcss.com/docs

Step 1: Detect Tailwind Version

Always check the version before giving any advice. v3 and v4 are fundamentally different.

Check package.json for the installed version:

json
{ "tailwindcss": "^3.x" }  // → v3 rules apply{ "tailwindcss": "^4.x" }  // → v4 rules apply

Also check for these signals:

SignalVersion
tailwind.config.js existsv3
@import "tailwindcss" in CSSv4
@tailwindcss/vite in dependenciesv4
@tailwindcss/postcss in dependenciesv4
@theme {} block in CSSv4

If v3: Apply resp-, dark-, comp-, config- rules. Note that v4 is available. If v4: Apply v4- rules. tailwind.config.js patterns do NOT apply — use @theme {} instead. If migrating v3 → v4: Follow v4-migration rules directly.

When to Apply

Reference these guidelines when:

  • Writing responsive layouts
  • Implementing dark mode
  • Creating reusable component styles
  • Configuring Tailwind (v3 or v4)
  • Migrating a project from v3 to v4
  • Setting up a new project with v4

Rule Categories by Priority

PriorityCategoryImpactPrefixVersion
1Responsive DesignCRITICALresp-v3 / v4
2Dark ModeCRITICALdark-v3 / v4
3Component PatternsHIGHcomp-v3 / v4
4Custom ConfigurationHIGHconfig-v3
5V4 & MigrationHIGHv4-v4 only
6Spacing & TypographyMEDIUMspace-v3 / v4
7AnimationMEDIUManim-v3 / v4
8PerformanceLOWperf-v3 / v4

Quick Reference

1. Responsive Design (CRITICAL)

  • resp-mobile-first - Mobile-first approach
  • resp-breakpoints - Use breakpoints correctly
  • resp-container - Container patterns
  • resp-grid-flex - Grid vs Flexbox decisions
  • resp-hidden-shown - Conditional display

2. Dark Mode (CRITICAL)

  • dark-setup - Configure dark mode
  • dark-classes - Apply dark mode classes
  • dark-toggle - Implement dark mode toggle
  • dark-system-preference - Respect system preference
  • dark-colors - Design for both modes

3. Component Patterns (HIGH)

  • comp-clsx-cn - Conditional classes utility
  • comp-variants - Component variants pattern
  • comp-slots - Slot-based components
  • comp-composition - Composing utilities

4. Custom Configuration — v3 only (HIGH)

  • config-extend - Extend vs override theme
  • config-colors - Custom color palette
  • config-fonts - Custom fonts
  • config-screens - Custom breakpoints
  • config-plugins - Using plugins

5. V4 & Migration (HIGH)

  • v4-installation - Install v4 with Vite or PostCSS, @source, @reference
  • v4-theme-configuration - Replace tailwind.config.js with @theme {} in CSS
  • v4-custom-utilities - @utility, @custom-variant, @variant, @plugin
  • v4-migration - Step-by-step v3 → v4 migration with renamed utilities, starting:, forced-colors:

6. Spacing & Typography (MEDIUM)

  • space-consistent - Consistent spacing scale
  • space-margins - Margin patterns
  • space-padding - Padding patterns
  • typo-scale - Typography scale
  • typo-line-height - Line height

7. Animation (MEDIUM)

  • anim-transitions - Transition utilities
  • anim-keyframes - Custom keyframes
  • anim-reduced-motion - Respect motion preferences

8. Performance (LOW)

  • perf-purge - Content configuration
  • perf-jit - JIT mode benefits
  • perf-arbitrary - Arbitrary values usage

Essential Patterns

Mobile-First Responsive Design

tsx
// ✅ Mobile-first: start with mobile, add larger breakpoints<div className="  w-full           // Mobile: full width  md:w-1/2         // Tablet: half width  lg:w-1/3         // Desktop: third width">  <p className="    text-sm          // Mobile: small text    md:text-base     // Tablet: base text    lg:text-lg       // Desktop: large text  ">    Content  </p></div>
// ❌ Don't think desktop-first<div className="w-1/3 md:w-1/2 sm:w-full">  // Confusing

Dark Mode Implementation

v3 — tailwind.config.js:

js
module.exports = { darkMode: 'class' }

v4 — CSS only, no config file:

css
@import "tailwindcss";/* dark mode is class-based by default in v4 — no config needed */

Component — identical in both versions:

tsx
<div className="bg-white dark:bg-gray-900 text-gray-900 dark:text-white">  <h2 className="text-gray-900 dark:text-white">Title</h2>  <p className="text-gray-600 dark:text-gray-400">Description</p></div>
function toggleDarkMode() {  document.documentElement.classList.toggle('dark')}

Conditional Classes with clsx/cn

tsx
import { clsx, type ClassValue } from 'clsx'import { twMerge } from 'tailwind-merge'
// cn utility - merges Tailwind classes intelligentlyexport function cn(...inputs: ClassValue[]) {  return twMerge(clsx(inputs))}
// Usageinterface ButtonProps {  variant?: 'primary' | 'secondary' | 'danger'  size?: 'sm' | 'md' | 'lg'  className?: string  children: React.ReactNode}
function Button({ variant = 'primary', size = 'md', className, children }: ButtonProps) {  return (    <button      className={cn(        // Base styles        'inline-flex items-center justify-center rounded-md font-medium transition-colors',        'focus:outline-none focus:ring-2 focus:ring-offset-2',
        // Variants        {          'bg-blue-600 text-white hover:bg-blue-700 focus:ring-blue-500':            variant === 'primary',          'bg-gray-100 text-gray-900 hover:bg-gray-200 focus:ring-gray-500':            variant === 'secondary',          'bg-red-600 text-white hover:bg-red-700 focus:ring-red-500':            variant === 'danger',        },
        // Sizes        {          'px-3 py-1.5 text-sm': size === 'sm',          'px-4 py-2 text-base': size === 'md',          'px-6 py-3 text-lg': size === 'lg',        },
        // Allow override        className      )}    >      {children}    </button>  )}

Theme Configuration — v3 vs v4

v3 — tailwind.config.js:

js
/** @type {import('tailwindcss').Config} */module.exports = {  content: ['./resources/**/*.{blade.php,js,ts,jsx,tsx}'],  darkMode: 'class',  theme: {    extend: {      colors: { primary: { 500: '#0ea5e9', 600: '#0284c7' } },      fontFamily: { sans: ['Inter', 'sans-serif'] },      spacing: { '18': '4.5rem' },    },  },  plugins: [require('@tailwindcss/forms')],}

v4 — app.css only, no JS config:

css
@import "tailwindcss";
@theme {  --color-primary-500: #0ea5e9;  --color-primary-600: #0284c7;  --font-sans: Inter, sans-serif;  --spacing-18: 4.5rem;  --breakpoint-3xl: 1920px;}

See v4-theme-configuration and v4-migration rules for full details.

Responsive Grid Layout

tsx
// Product grid - responsive columns<div className="grid grid-cols-1 sm:grid-cols-2 lg:grid-cols-3 xl:grid-cols-4 gap-6">  {products.map(product => (    <ProductCard key={product.id} product={product} />  ))}</div>
// Dashboard layout - sidebar + main<div className="flex flex-col lg:flex-row min-h-screen">  <aside className="    w-full lg:w-64    bg-gray-900    lg:min-h-screen  ">    <nav>...</nav>  </aside>  <main className="flex-1 p-4 lg:p-8">    <div className="max-w-7xl mx-auto">      {children}    </div>  </main></div>

Form Styling

tsx
<form className="space-y-6">  <div>    <label htmlFor="email" className="block text-sm font-medium text-gray-700 dark:text-gray-300">      Email    </label>    <input      type="email"      id="email"      className="        mt-1 block w-full rounded-md        border-gray-300 dark:border-gray-600        bg-white dark:bg-gray-800        text-gray-900 dark:text-white        shadow-sm        focus:border-blue-500 focus:ring-blue-500        disabled:bg-gray-100 disabled:cursor-not-allowed      "    />  </div>
  <button    type="submit"    className="      w-full flex justify-center      py-2 px-4      border border-transparent rounded-md      shadow-sm text-sm font-medium      text-white bg-blue-600      hover:bg-blue-700      focus:outline-none focus:ring-2 focus:ring-offset-2 focus:ring-blue-500      disabled:opacity-50 disabled:cursor-not-allowed    "  >    Submit  </button></form>

Animations with Reduced Motion

tsx
// Respect user's motion preferences<div className="  transition-transform duration-300  hover:scale-105  motion-reduce:transition-none  motion-reduce:hover:transform-none">  Card content</div>
// Custom animation<div className="animate-fade-in motion-reduce:animate-none">  Content</div>
js
// tailwind.config.jsmodule.exports = {  theme: {    extend: {      keyframes: {        'fade-in': {          '0%': { opacity: '0' },          '100%': { opacity: '1' },        },      },      animation: {        'fade-in': 'fade-in 0.3s ease-out',      },    },  },}

How to Use

Always run Step 1 (version detection) first, then read the relevant rule files:

v3 projects:

rules/config-extend-theme.mdrules/dark-setup.mdrules/comp-clsx-cn.mdrules/resp-mobile-first.md

v4 projects:

rules/v4-installation.mdrules/v4-theme-configuration.mdrules/v4-custom-utilities.md

Migrating v3 → v4:

rules/v4-migration.md

References

Ecosystem Tools

  • Tailwind CSS IntelliSense - VS Code autocomplete and linting
  • Prettier Plugin - Automatic class sorting
  • tailwind-merge - Conflict-free class merging
  • clsx - Conditional class utility
  • CVA - Component variant system

License

MIT License - See repository for full license text.

This skill is part of the Agent Skills collection, providing AI-powered development assistance with industry best practices.

Source and attribution

Source:asyrafhussin/agent-skillsinskills/tailwind-best-practicesat commit1aa0ff7

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal