Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Tailwind CSS v3 to v4 Upgrade with Visual Regression Check

    1

    Upgrade Tailwind v3 to v4 and catch what the tool misses: dynamic classes, new border, ring and hover defaults, @apply in Vue/Svelte. UPGRADED / REVIEW VISUALS / STAY ON V3.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Tailwind CSS v3 to v4 Upgrade with Visual Regression Check

    Tailwind CSS v3 to v4 Upgrade with Visual Regression Check

    Example session with this skill installed

    Upgrade our Next.js 15 app from Tailwind 3.4 to v4. We use cva for buttons, @tailwindcss/forms and typography, and a few CSS modules with @apply. Support target is last 2 versions of major browsers. Tell me what will look different.

    • Read your context and instructions
    • Compiled the tailwind css v3
    • Generated the UI component

    Tailwind upgrade: storefront — VERDICT: REVIEW VISUALS

    Go / no-go

    CheckResult
    Browser targetsLast 2 versions: all above Safari 16.4 / Chrome 111 / Firefox 128. Go
    Sass/Less/StylusNone. Go
    Node22.14. Go
    Pluginsforms and typography have v4 releases; loaded with @plugin. Go

    What the upgrade tool changed

    63 files: @import "tailwindcss", theme moved to @theme, 214 class renames in JSX, PostCSS switched to @tailwindcss/postcss, autoprefixer removed.

    Fixed by hand (tool could not see these)

    AreaFilesChangeWhy
    cva variantscomponents/ui/button.tsshadow → shadow-sm, rounded → rounded-sm, outline-none → outline-hiddenclasses live in a TS object
    Constantslib/badge-styles.tsbg-opacity-50 → /50 modifierremoved utility
    CSS modules4 *.module.cssadded @reference "../app/globals.css";@apply could not find theme
    Stacked variantsProductGrid.tsxfirst:*:pt-0 → *:first:pt-0left-to-right order

    Visual differences to decide

    PageDifferenceCauseProposed
    Checkoutinput borders now near-blackborder default is currentColoradd border-gray-200 base style
    All formsfocus ring 1px, darkring default 1px currentColorring-3 ring-blue-500 in Input
    Searchplaceholder darkernew Preflight placeholder coloraccept
    Buttonsarrow cursorPreflight cursor: defaultadd pointer base style
    Mobile navhover tint no longer sticks after taphover needs (hover: hover)accept (improvement)

    Build and tests

    next build pass · vitest 212/212 pass · CSS 41.8 KB → 37.2 KB gzip.

    Screenshots for checkout and account were not compared (pages need a logged-in session). Verdict stays REVIEW VISUALS until you confirm the 5 decisions and check those 2 pages.

    module.css

    TSX · React component

    Generated

    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

    npx @tailwindcss/upgrade does a lot, but it cannot see class names built in JavaScript, and several v4 changes keep the same class name while changing the look. Borders turn black, focus rings get thinner, placeholders change color, buttons lose the pointer cursor, and hover styles stop on touch screens. The build passes, so nobody notices until users do.

    This skill gives your coding agent a fixed upgrade procedure and a reference file checked against the official Tailwind v4 upgrade guide. It:

    • Runs a go / no-go check first: Safari 16.4+, Chrome 111+, Firefox 128+, no Sass/Less/Stylus, Node 20+, unsupported config options (corePlugins, safelist, separator, resolveConfig), and plugin support
    • Takes baseline screenshots of key pages at desktop and mobile widths before changing anything
    • Runs the official upgrade tool, then hunts for what it misses: classes in clsx/cva/template literals/constants/CMS content, using the full rename and removal tables (and the right order, so shadow-sm is not renamed twice)
    • Handles changed defaults: border color, ring width and color, outline-none vs outline-hidden, placeholder, button cursor, dialog margin, hidden attribute, hover media query, space-* and divide-* selectors
    • Fixes syntax changes: variant order, trailing !, tw: prefix, bg-(--var), @utility, @reference for @apply in Vue/Svelte/CSS modules, theme() to CSS variables, container options, transforms
    • Compares after screenshots and lists every visual difference with its cause and a decision
    • Returns a verdict: UPGRADED, REVIEW VISUALS or STAY ON V3

    Who it is for: frontend developers and agencies upgrading Next.js, Vite, Laravel, Rails, Vue, Svelte or Astro projects to Tailwind v4.

    Safety: works on a new branch, asks before installing packages or removing tailwind.config.js, and never claims the UI is unchanged without a real comparison.

    Honesty note: if screenshots could not be taken, the verdict stays at REVIEW VISUALS and the report says which pages to check by hand.

    Requires Node 20+. Cannot upgrade projects using Sass/Less/Stylus preprocessors. Browser support limited to Safari 16.4+, Chrome 111+, and Firefox 128+.

    How to use

    1. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 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 29 days ago

    Requires

    @tailwindcss/upgrade
    Node.js
    tailwindcss
    @tailwindcss/cli

    Permissions

    Terminal / Shell
    Browser
    Read Files
    Write Files
    Listed29 days ago

    What's inside

    Frequently Asked Questions

    While the official CLI handles standard renames, this skill identifies "stealth" bugs like dynamic class strings in JS/TS files and visual regressions in default border/ring colors that automated scripts often miss.

    This skill supports all modern frontend frameworks including React, Vue, and Svelte, provided your project uses Node.js 20+ and doesn't rely on Sass/Less preprocessors for Tailwind directives.

    Before changing anything, your agent takes screenshots of 5 to 15 key pages at desktop and mobile widths, using Playwright or a similar tool if your project has one. After the upgrade it takes the same screenshots and lists every visible difference with its cause and a proposed fix. If screenshots cannot be taken, the verdict stays at REVIEW VISUALS and you get a list of pages to check by hand.

    Yes. It searches cva variant objects, clsx calls, template literals, constants and other places where class names are built in code, using the full rename and removal tables, because the official upgrade tool cannot always see these.

    A SKILL.md with the upgrade procedure and verdict rules, plus a reference file with the v4 requirements, removed and renamed utilities, changed defaults with the base styles to keep the v3 look, and syntax changes. Your agent produces a go/no-go check, the code changes, a visual comparison table and a verdict.

    No, v4 requires a modern CSS environment; this skill will flag unsupported browser targets or legacy CSS preprocessors during the pre-flight audit before making any changes.

    New in Frontend & Web Apps