tailwind-v4-migration

tailwind-v4-migration is a cursor rule for Cursor from RoninForge/roninforge-tailwind-v4. It costs 36 tokens per session (1,786 once invoked), scanned A, original, MIT.

A set of instructions for moving a project from Tailwind CSS version 3 to version 4. Tailwind CSS is a tool for styling web pages with predefined utility classes.

In plain words
What is it for?
Use it when upgrading Tailwind CSS dependencies, class names, CSS imports, configuration, or PostCSS settings from version 3 to version 4.
Why use it?
It explains the upgrade steps, browser and Node.js requirements, automated migration, and cases that still need manual review. This helps avoid broken styles and unsupported browser setups.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is @config "../../tailwind.config.js";.

Good fit Use it when upgrading Tailwind CSS dependencies, class names, CSS imports, configuration, or PostCSS settings from version 3 to version 4.

Compare 6 cursor rules from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/RoninForge/roninforge-tailwind-v4
agentmods
npx agentmods add rules/roninforge/roninforge-tailwind-v4/tailwind-v4-migration

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for tailwind-v4-migration

README.md
[![agentmods](https://agentmods.dev/badge/rules/roninforge/roninforge-tailwind-v4/tailwind-v4-migration/github.svg)](https://agentmods.dev/rules/roninforge/roninforge-tailwind-v4/tailwind-v4-migration)
Your own site
<a href="https://agentmods.dev/rules/roninforge/roninforge-tailwind-v4/tailwind-v4-migration"><img src="https://agentmods.dev/badge/rules/roninforge/roninforge-tailwind-v4/tailwind-v4-migration/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for tailwind-v4-migration

Your own site · 80×15
<a href="https://agentmods.dev/rules/roninforge/roninforge-tailwind-v4/tailwind-v4-migration"><img src="https://agentmods.dev/badge/rules/roninforge/roninforge-tailwind-v4/tailwind-v4-migration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,786 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.01786
Opus 5.5 $0.00014 $0.00714
Sonnet 5.5 $0.00007 $0.00357
Haiku 4.5 $0.00004 $0.00179

Measured 1mo ago against content hash 633499343718, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

tailwind-v4-migration scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

rules/tailwind-v4-migration.mdc · 291 lines

How it starts

The opening of the file, as written. The whole thing — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Tailwind v3 to v4 Migration

Use these rules when migrating an existing Tailwind v3 project to v4. For a full interactive migration workflow, use the /tw-migrate skill.

Before Starting

Browser requirement: v4 requires Safari 16.4+, Chrome 111+, Firefox 128+. If the project needs older browser support, stay on v3.4.x.

Node.js requirement: The @tailwindcss/upgrade tool requires Node.js 20+. Tailwind v4 itself supports Node.js 18+.

Automated Upgrade Tool

Tailwind provides an automated upgrade tool that handles many changes:

npx @tailwindcss/upgrade

This tool:

  • Converts @tailwind imports to @import "tailwindcss"
  • Moves ! important modifiers to class end
  • Updates arbitrary CSS variable syntax [--x] to (--x)
  • Renames utility classes (shadow-sm to shadow-xs, etc.)
  • Updates PostCSS config
  • Attempts to convert tailwind.config.js to @theme

It does NOT handle all edge cases. Manual review is always required after running it.

Manual Migration Steps

Step 1: Update Dependencies

# Remove v3 packages
npm uninstall tailwindcss autoprefixer postcss-import

# Install v4 packages (choose one)
npm install -D tailwindcss @tailwindcss/vite       # Vite projects
npm install -D tailwindcss @tailwindcss/postcss     # PostCSS projects

Step 2: Update CSS Entry Point

Replace:

@tailwind base;
@tailwind components;
@tailwind utilities;

With:

@import "tailwindcss";

Step 3: Convert Configuration

Move tailwind.config.js theme values to @theme:

// OLD: tailwind.config.js
module.exports = {
  theme: {
    extend: {
      colors: {
        brand: '#ff6a00',
      },
      fontFamily: {
        sans: ['Inter', 'sans-serif'],
      },
    },
  },
}
/* NEW: in your CSS file */
@import "tailwindcss";

@theme {
  --color-brand: #ff6a00;
  --font-sans: "Inter", sans-serif;
}

If full conversion is not yet practical, bridge with @config:

@import "tailwindcss";
@config "../../tailwind.config.js";

Read the full file on GitHub · 291 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 291 lines · 36 tokens per session scan A 633499343718

Subscribe to this mod's changes

tailwind-v4-migration is a cursor rule published in the GitHub repository RoninForge/roninforge-tailwind-v4 (2 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 1,786 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.