tailwindcss-development

Styles application components using Tailwind CSS v4 utilities and CSS-first configuration.

1|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/mst-software-vn/mst-checkscam --skill tailwindcss-development-mst-software-vn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tailwindcss-development
Source: https://github.com/mst-software-vn/mst-checkscam/tree/main/.claude/skills/tailwindcss-development
Command: npx skills add https://github.com/mst-software-vn/mst-checkscam --skill tailwindcss-development-mst-software-vn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Applying consistent, modern styling with Tailwind CSS v4 requires knowing its new CSS-first configuration, updated import syntax, and which v3 utilities were removed. This Skill guides correct usage of Tailwind v4 so components are styled without deprecated patterns or configuration mistakes. ## Core Features & Use Cases - Tailwind v4 Migration Guidance: Replaces deprecated utilities (bg-opacity-, flex-shrink-, etc.) with their v4 equivalents and uses @import "tailwindcss" instead of @tailwind directives. - CSS-First Configuration: Defines design tokens via the @theme directive in CSS instead of a tailwind.config.js file. - Layout & Dark Mode Patterns: Provides flexbox, grid, gap-based spacing, and dark: variant patterns for responsive, theme-aware components. - Use Case: When restyling a hero section or building a responsive card grid, the Skill ensures correct v4 syntax, consistent spacing with gap utilities, and dark mode support matching the project's conventions. ## Quick Start Style this component with Tailwind CSS v4, using a responsive grid layout, gap spacing, and dark mode variants.

Frequently Asked Questions about tailwindcss-development

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

FAQPage Schema
How do I configure Tailwind CSS v4 without tailwind.config.js?▼

Tailwind CSS v4 uses CSS-first configuration with the @theme directive directly in your stylesheet. Define custom tokens like colors inside @theme blocks, for example --color-brand, instead of maintaining a separate JavaScript config file.

How to migrate from Tailwind CSS v3 to v4 import syntax?▼

Replace the three @tailwind base, components, and utilities directives with a single @import "tailwindcss" statement. Also update deprecated utilities such as bg-opacity-* to bg-black/* and flex-shrink-* to shrink-*.

Does Tailwind CSS v4 support dark mode?▼

Yes, Tailwind CSS v4 supports dark mode using the dark: variant on utilities, such as dark:bg-gray-900. New components should follow the same dark mode approach already used by existing pages in the project.

Why is corePlugins not working in Tailwind CSS v4?▼

The corePlugins option is not supported in Tailwind CSS v4 because configuration moved to a CSS-first model. Control which utilities are used through your CSS imports and @theme configuration instead of the old JavaScript config.

Should I use margin or gap for spacing between flex items in Tailwind?▼

Use gap utilities like gap-4 or gap-8 on the flex or grid container rather than margins on child elements. This keeps spacing consistent, avoids margin-collapse issues, and reduces redundant classes across sibling elements.