- Home
- Skills
- Frontend & Web Apps
- Tailwind CSS v4 Migration Check
More screenshots
Works with the AI Agents you already use
Tailwind CSS v4 Migration Check
You bump tailwindcss to v4 and the build stops with "It looks like you're trying to use tailwindcss directly as a PostCSS plugin".
$5
Tailwind CSS v4 Migration Check
Example session with this skill installed
Check this project with tailwind-v4-migration-check.
- Read your context and instructions
- Compiled the tailwind css v4
- Generated the UI component
$ python3 scripts/check_tailwind.py examples/risky
BLOCK package.json:7 T01 V3_TOOLING_WITH_V4
"build:css": "tailwindcss -i ./src/styles/main.css -o ./public/app.css --minify"
Why: Tailwind CSS v4 is installed, but this file still uses the v3 tooling. In v4 the PostCSS plugin moved to @tailwindcss/postcss (tailwindcss as a PostCSS plugin stops the build with an error), Vite uses @tailwindcss/vite, the CLI moved to @tailwindcss/cli (the tailwindcss package has no command any more), and tailwindcss/nesting no longer exists.
Safer: Use "@tailwindcss/postcss": {} in the PostCSS config (postcss-import and autoprefixer are no longer needed), import tailwindcss from "@tailwindcss/vite" in vite.config, and run npx @tailwindcss/cli -i input.css -o output.css with @tailwindcss/cli in devDependencies.
BLOCK postcss.config.js:3 T01 V3_TOOLING_WITH_V4
BLOCK src/components/Overlay.tsx:6 T04 REMOVED_CLASS_SYNTAX
BLOCK src/components/Overlay.tsx:7 T04 REMOVED_CLASS_SYNTAX
BLOCK src/components/SaveButton.vue:14 T05 APPLY_CANNOT_RESOLVE
BLOCK src/styles/main.css:1 T02 V3_DIRECTIVE_REMOVED
BLOCK src/styles/main.css:2 T02 V3_DIRECTIVE_REMOVED
BLOCK src/styles/main.css:3 T02 V3_DIRECTIVE_REMOVED
BLOCK src/styles/main.css:20 T05 APPLY_CANNOT_RESOLVE
BLOCK src/styles/main.css:28 T04 REMOVED_CLASS_SYNTAX
BLOCK src/styles/main.css:31 T02 V3_DIRECTIVE_REMOVED
BLOCK tailwind.config.js:4 T03 JS_CONFIG_NOT_APPLIED
BLOCK tailwind.config.js:5 T03 JS_CONFIG_NOT_APPLIED
REVIEW admin/package.json:7 T11 V4_NOT_INSTALLED
REVIEW docs/tailwind.config.js:3 T19 JS_CONFIG_NOT_LOADED
REVIEW package.json:10 T17 PLUGIN_OR_LIBRARY_NOT_LOADED
REVIEW package.json:14 T17 PLUGIN_OR_LIBRARY_NOT_LOADED
REVIEW package.json:15 T17 PLUGIN_OR_LIBRARY_NOT_LOADED
REVIEW package.json:25 T16 BROWSER_TARGETS_BELOW_V4
REVIEW src/components/Overlay.tsx:7 T12 CLASS_MEANING_CHANGED
REVIEW src/components/SaveButton.vue:2 T12 CLASS_MEANING_CHANGED
REVIEW src/components/SaveButton.vue:5 T13 BORDER_COLOR_DEFAULT_CHANGED
REVIEW src/styles/legacy.scss:2 T18 PREPROCESSOR_WITH_V4
REVIEW src/styles/main.css:8 T14 THEME_FUNCTION_DEPRECATED
REVIEW src/styles/main.css:13 T15 CUSTOM_UTILITY_IN_LAYER
REVIEW src/styles/main.css:34 T14 THEME_FUNCTION_DEPRECATED
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 11 files, 11 with Tailwind CSS content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
main.css
TSX · React component
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
You bump tailwindcss to v4 and the build stops with "It looks like you're trying to use tailwindcss directly as a PostCSS plugin". You fix that, and now the dark mode toggle does nothing because v4 never loads your tailwind.config.js, every bg-opacity-50 overlay is solid, and the Vue component with @apply fails with "Cannot apply unknown utility class". This skill finds those leftovers and the others listed below in one pass, and tells you how to fix each one.
Your agent runs a scanner on your package.json files, PostCSS and Vite configs, tailwind.config files, browserslist, stylesheets (CSS, Sass, Less, Stylus), Vue, Svelte and Astro components with their style blocks, React and other JavaScript or TypeScript, and HTML-like templates (Blade, ERB, Twig, Liquid, Nunjucks and more). It works out the Tailwind CSS version of each app from its package.json, so a monorepo with one app still on v3 is checked per app, and v3 code is not flagged until that app upgrades. It reads class names from class and className attributes, Vue, Angular and Astro class bindings, cn(), clsx(), cva(), twMerge() and @apply, and skips comments, code samples, node_modules, build output and generated CSS. It never runs a build or installs anything. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach, and each rule links to the official Tailwind CSS documentation behind it. Secrets are never printed.
What it checks
BLOCK
- T01: tailwindcss used as a PostCSS or Vite plugin (also in the postcss field of package.json), tailwindcss/nesting, and scripts that run the v3 tailwindcss command without @tailwindcss/cli
- T02: @tailwind base and components, @screen, screen() and imports of tailwindcss/base or tailwindcss/components
- T03: a tailwind.config.js that no @config loads and whose settings have no CSS counterpart yet (darkMode, plugins, content paths, prefix, presets), and the safelist, corePlugins and separator options v4 does not support
- T04: bg-, text-, border-, divide-, ring- and placeholder-opacity classes, and CSS variables in square brackets such as bg-[--brand]
- T05: @apply of theme utilities, including your own @theme colors, fonts and breakpoints, in Vue, Svelte or Astro style blocks, CSS modules, Angular component styles and stylesheets imported from component code, without @reference; and @apply of classes defined in @layer instead of @utility
REVIEW
- T11: apps that use Tailwind CSS but are not on v4 yet (v3 in package.json, the v3 Play CDN, or no version found)
- T12: classes that still work but look different or are deprecated: ring, outline-none without a focus style, shadow-sm, rounded-sm and blur-sm in a project that still uses the bare v3 names of those scales, flex-grow, flex-shrink, overflow-ellipsis, decoration-slice and decoration-clone
- T13: borders without a color (now the text color instead of gray) when no base style restores the old color
- T14: theme() with the v3 dot path, such as theme(colors.gray.200)
- T15: custom classes in @layer utilities (no hover:, md: or dark: variants in v4)
- T16: browser targets older than Safari 16.4, Chrome 111 or Firefox 128 in browserslist or Vite build.target, and @vitejs/plugin-legacy
- T17: Tailwind plugins in package.json with no @plugin line, container-queries and line-clamp plugins that v4 has built in, and Flowbite or Preline without an @source line
- T18: Tailwind v4 at-rules in Sass, Less or Stylus files
- T19: a tailwind.config.js that nothing loads and that looks left over (its settings already live in @theme, @custom-variant, @plugin or @source, or it holds only theme values)
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason, safer approach and official source link for each rule
- A risky and a safe example project (a Vue storefront half-way through the upgrade, with a v3 admin app and a leftover docs config beside it), and the real report the scanner produces on the risky one
Limits It reads file text and does not run Tailwind, so classes built at run time (string concatenation, values from a CMS) and what a loaded JS config resolves to are not seen. The prefix, important-modifier, variant-order, space-between and gradient changes are not checked, and the version comes from the range in package.json, not the lock file. The meaning-changed, border, plugin and leftover-config rules are hints to confirm in the browser. NOT FLAGGED is not a guarantee.
Static check of config, stylesheet and template text. The installed Tailwind CSS version, classes built at run time and the rendered page are not checked. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 days ago
Requires
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example projects are plain text files (package.json, configs, CSS, Vue and TSX) with no dependencies installed. Nothing in them is run.