Tailwind CSS v4 operator

Operate Tailwind CSS v4 Vite, PostCSS, CLI, and webpack builds, automatic detection, source base paths, explicit and inline sources, exclusions, watch mode, minification, and output. Use when classes must be discovered reliably or a v4 build boundary needs a focused change.

Look up Tailwind CSS v4 commands, build adapters, source detection, CSS-first themes, custom utilities, variants, compatibility directives, and migration patterns. Use when the user wants a concise v4 reference instead of a guided workflow.

Inspect Tailwind CSS v4 core and adapter versions, scripts, CSS entry, automatic and explicit sources, theme variables, compatibility directives, plugins, generated output, and browser requirements without changing them. Use when the user asks what v4 setup exists or needs a safe baseline.

Connect Tailwind CSS v4 to framework build pipelines, CSS modules and component styles, editors, monorepos, component libraries, tests, continuous integration, and deployment with end-to-end checks. Use when the task concerns the seam between Tailwind v4 and another system.

Plan, preview, execute, review, and verify Tailwind CSS v3-to-v4 migrations across packages, build adapters, CSS imports, configuration, utilities, variants, templates, browser requirements, and plugins. Use when the user explicitly asks to upgrade an existing v3 project to v4.

Operate Tailwind CSS v4 CSS plugins, JavaScript plugin compatibility, explicit config loading, source safelists, references, prefixes, important modifiers, Preflight, and legacy integration seams. Use when v4 must consume a plugin or retain bounded behavior from a v3-era setup.

Install and configure Tailwind CSS v4 with aligned version constraints, one deliberate Vite, PostCSS, CLI, or webpack adapter, a CSS import, source ownership, and one verified template. Use when a project has no Tailwind setup or the user explicitly asks to initialize v4.

Manage Tailwind CSS v4 theme variable namespaces, tokens, default resets, static emission, shared theme packages, runtime CSS variable access, and responsive design values. Use when the user asks to customize or review the v4 CSS-first design system.

Diagnose Tailwind CSS v4 core and adapter mismatches, source detection, theme, plugin, compatibility, browser, watch, missing-style, and oversized-output failures from exact evidence. Use when a v4 build fails, classes are absent or ineffective, or generated CSS behaves unexpectedly.

Author and refactor Tailwind CSS v4 utility compositions, arbitrary values, custom utility definitions, custom variants, responsive and container behavior, state modifiers, and apply usage. Use when the user asks to style an interface or define a reusable v4 utility or variant.