tailwind-best-practices

Correct outdated Tailwind CSS v3 patterns to v4 syntax.

3|Updated May 5, 2026
One-click install
npx skills add https://github.com/bryanvillamilpragma/power-Pragma --skill tailwind-best-practices-bryanvillamilpragma
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tailwind-best-practices
Source: https://github.com/bryanvillamilpragma/power-Pragma/tree/main/skills-registry/tailwind-best-practices
Command: npx skills add https://github.com/bryanvillamilpragma/power-Pragma --skill tailwind-best-practices-bryanvillamilpragma

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures your AI agent generates up-to-date Tailwind CSS v4 code, avoiding outdated patterns and anti-patterns.

Core Features & Use Cases

  • Enforce v4 Syntax: Corrects common errors related to deprecated directives and utilities.
  • CSS-First Configuration: Recommends the use of CSS-first configuration with @theme.
  • Modern Patterns: Encourages the use of modern opacity syntax, CSS variables, and container queries.
  • Custom Utilities: Provides guidance on creating custom utilities with @utility.
  • Use Case: For developers who want to ensure their AI agents write modern, maintainable Tailwind CSS code.

Quick Start

Use the tailwind-best-practices skill to analyze your Tailwind CSS code and apply the latest best practices.

Frequently Asked Questions about tailwind-best-practices

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

FAQPage Schema
How do I migrate outdated Tailwind CSS v3 patterns to v4 syntax?

Tailwind CSS v4 replaces JS config with CSS-first configuration using the @theme directive, enabling you to define design tokens directly in CSS and generate utilities automatically.

How do I configure Tailwind CSS v4 using CSS-first configuration?

Tailwind CSS v4 replaces JS config with CSS-first configuration using the @theme directive, enabling you to define design tokens directly in CSS and generate utilities automatically.

What is the best way to create custom utilities in Tailwind CSS v4?

The best way to create custom utilities in Tailwind CSS v4 is using the @utility directive, which ensures your custom classes integrate cleanly with modern utility patterns and avoid common anti-patterns.

Does Tailwind CSS v4 support modern opacity syntax and container queries?

Tailwind CSS v4 supports modern opacity syntax and container queries, encouraging the use of CSS variables and modern utility patterns to maintain up-to-date, maintainable code.

What are common anti-patterns to avoid when writing Tailwind CSS v4?

Common Tailwind CSS v4 anti-patterns include using deprecated v3 directives, relying on outdated JS configuration instead of CSS-first @theme setup, and ignoring modern utility patterns for opacity and custom utilities.