tailwind

Configure Tailwind v4 styles directly in CSS without tailwind.config.js.

40|2|Updated Sep 24, 2025
One-click install
npx skills add https://github.com/remorses/opencode-config --skill tailwind-remorses
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tailwind
Source: https://github.com/remorses/opencode-config/tree/main/skills/tailwind
Command: npx skills add https://github.com/remorses/opencode-config --skill tailwind-remorses

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tailwind v4 conventions and CSS-based configuration eliminate the need for a separate tailwind.config.js by configuring styles directly in CSS.

Core Features & Use Cases

  • Enforces CSS-based Tailwind v4 configuration, enabling in-file theming and consistent design tokens.
  • Promotes dark mode handling via @variant dark and nested CSS rules for predictable theming.
  • Guides minimal, typography-friendly layouts with emphasis on spacing, gaps, and component reuse instead of card-based grouping.
  • Encourages reuse of existing UI components (components/ui) and avoids redeclaration of shared primitives.
  • Provides guidance on CSS custom properties, token bridging with @theme inline, and scalable theming patterns.

Quick Start

Follow Tailwind v4 CSS conventions, enable dark mode with @variant dark, and configure styles directly in CSS without a tailwind.config.js.

Frequently Asked Questions about tailwind

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

FAQPage Schema
How do I configure Tailwind v4 without a tailwind.config.js file?

Tailwind v4 enables CSS-based configuration directly in your stylesheet, eliminating the need for a separate tailwind.config.js file. You define design tokens and custom properties natively in CSS, streamlining your theming setup and reducing configuration overhead.

What is the best way to implement dark mode in Tailwind v4?

Dark mode in Tailwind v4 is implemented using the @variant dark directive alongside nested CSS rules. This approach provides predictable theming behavior by scoping dark styles directly within your component CSS.

How do I manage design tokens and scalable theming in Tailwind v4?

You manage scalable theming in Tailwind v4 by using CSS custom properties and the @theme inline directive for token bridging. This method enforces in-file theming to ensure consistent UI design tokens across your project.

Does Tailwind v4 require a specific folder structure for UI components?

Tailwind v4 encourages reusing existing UI components from a components/ui directory and avoiding the redeclaration of shared primitives. It guides minimal layouts focused on spacing and gaps rather than card-based grouping.

Can I use Tailwind v4 for typography-friendly layouts instead of card-based grouping?

Yes, Tailwind v4 guides minimal, typography-friendly layouts with a strong emphasis on spacing, gaps, and component reuse. This approach intentionally avoids card-based grouping to ensure predictable and consistent UI.