tailwind-validator

Validate Tailwind CSS v4 CSS-first configuration and flag v3 patterns.

2|1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/genfeedai/genfeed.ai --skill tailwind-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tailwind-validator
Source: https://github.com/genfeedai/genfeed.ai/tree/main/.agents/skills/tailwind-validator
Command: npx skills add https://github.com/genfeedai/genfeed.ai --skill tailwind-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Validates that a project uses Tailwind CSS v4 with a CSS-first configuration and flags Tailwind v3 patterns to prevent migration issues.

Core Features & Use Cases

  • Detects Tailwind v4 CSS-first configuration and validates package versions.
  • Flags deprecated v3 patterns such as tailwind.config.js and old postcss setups.
  • Provides migration guidance and CI-friendly outputs to stop regressions.
  • Audits PostCSS configuration, CSS files, and theme usage to ensure CSS variables (@theme) are in place.
  • Works across new projects and existing codebases to accelerate safe Tailwind upgrades.

Quick Start

Run the validator in your project root to assess Tailwind v4 compatibility and flag v3 patterns.

Frequently Asked Questions about tailwind-validator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my project is ready for Tailwind CSS v4 migration?

To check Tailwind v4 readiness, validate that your project uses a CSS-first configuration and correct package versions while flagging deprecated v3 patterns like tailwind.config.js to prevent migration issues.

What is a CSS-first configuration in Tailwind CSS v4?

A CSS-first configuration in Tailwind CSS v4 replaces JavaScript config files by using CSS variables and the @theme directive within your CSS files to define theme tokens, ensuring a safe upgrade from older v3 patterns.

How do I flag deprecated Tailwind v3 patterns during an upgrade?

Flag deprecated Tailwind v3 patterns by auditing your PostCSS configuration, CSS files, and theme usage to identify old setups and ensure the required CSS variables are in place for v4.

Does the Tailwind v4 validator work for both new setups and existing codebases?

The Tailwind v4 validator works across new frontend projects and existing codebases, applying version checks and configuration audits to accelerate safe Tailwind upgrades and prevent regressions.

Can I get CI-friendly outputs when validating Tailwind v4 compatibility?

You can get CI-friendly outputs when validating Tailwind v4 compatibility, allowing you to stop regressions and enforce version, CSS structure, and PostCSS configuration requirements during automated frontend audits.