modern-tailwind

Apply Tailwind CSS utilities for styling instead of custom CSS.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/ddoman90/claude-code-intro --skill modern-tailwind
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: modern-tailwind
Source: https://github.com/ddoman90/claude-code-intro/tree/main/.claude/skills/modern-tailwind
Command: npx skills add https://github.com/ddoman90/claude-code-intro --skill modern-tailwind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build clean, scalable UI styles by embracing Tailwind CSS utilities over heavy custom CSS.

Core Features & Use Cases

  • Prefer utility classes over custom CSS for most styling
  • Keep class lists readable by grouping: layout → spacing → typography → color → effects
  • Use semantic HTML first; utilities should enhance, not replace structure
  • Use hover, focus-visible, disabled, dark, and motion-safe variants where appropriate
  • Prefer data-* and aria-* variants for stateful styling tied to DOM semantics
  • Use group and peer for parent/sibling state without extra JS
  • Start with base styles, then add responsive variants (sm, md, lg, ...)
  • Use container query utilities when layout depends on parent size
  • Extend the theme in tailwind.config instead of ad-hoc custom classes
  • Use @layer for custom utilities/components when repetition is unavoidable
  • AVOID @apply except for small, repeatable patterns
  • Extract reusable UI into components instead of repeating large class strings
  • Keep class names deterministic; avoid dynamic string concatenation when possible

Quick Start

Start by identifying a common component pattern and implement it with utility classes, then extract reusable tokens into Tailwind themes and layers.

Frequently Asked Questions about modern-tailwind

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

FAQPage Schema
How do I organize Tailwind CSS utility classes to keep them readable?

To keep Tailwind CSS utility classes readable, group class lists by category: layout, spacing, typography, color, and effects. This deterministic ordering maintains styling clarity and prevents messy class strings across components.

What's the best way to handle responsive design and state variants in Tailwind CSS?

Handle responsive design in Tailwind CSS by starting with base styles, then adding sm, md, and lg variants. Use hover, focus-visible, dark, and motion-safe variants, plus group and peer selectors for stateful styling without extra JavaScript.

Should I use @apply or custom CSS when building a Tailwind design system?

When building a Tailwind design system, prefer utility classes over custom CSS and avoid @apply except for small, repeatable patterns. Use @layer for unavoidable repetition and extract reusable UI into components instead of large class strings.

How do I scale theming in Tailwind CSS without writing ad-hoc custom classes?

Scale theming in Tailwind CSS by extending the theme configuration in tailwind.config instead of writing ad-hoc custom classes. This centralizes design tokens and ensures maintainable, consistent styling across web apps and component libraries.

Does Tailwind CSS support styling based on DOM semantics and parent container size?

Tailwind CSS supports DOM semantic styling using data-* and aria-* variants for stateful changes. For layout depending on parent size, use container query utilities alongside responsive variants to adapt designs without custom JavaScript logic.

Why should I avoid dynamic string concatenation for Tailwind CSS class names?

Avoid dynamic string concatenation for Tailwind CSS class names because it breaks deterministic class detection. Keep class names static and complete to ensure the compiler correctly identifies and generates the required utility styles.