PluginBench
Skill
Pass
Audit score 90

tailwind-patterns

sickn33/agentic-awesome-skills

Tailwind CSS v4 patterns: CSS-first configuration, container queries, and modern design token architecture.

What is tailwind-patterns?

Reference guide for Tailwind CSS v4 principles including CSS-based theme configuration, container queries, responsive design, and modern layout patterns. Use this when configuring Tailwind v4, implementing design tokens, or building component systems with utility-first CSS.

  • CSS-first theme configuration using @theme directives instead of JavaScript config
  • Container queries for component-level responsive design independent of viewport
  • Modern layout patterns with flexbox, grid, and asymmetric (Bento) layouts
  • OKLCH color system and semantic token architecture for design consistency
  • Dark mode strategies (class, media, selector) and implementation patterns
  • Typography system with font stacks and type scales

How to install tailwind-patterns

npx skills add https://github.com/sickn33/agentic-awesome-skills --skill tailwind-patterns
Claude Code
Cursor
Windsurf
Cline

How to use tailwind-patterns

  1. 1.Review the v4 architecture changes from v3 to understand CSS-first configuration
  2. 2.Define your theme using @theme directive with semantic color tokens and spacing scales
  3. 3.Choose a dark mode strategy (class, media, or selector) and implement accordingly
  4. 4.Use container queries (@container, @sm:, @md:) for component-level responsive design
  5. 5.Apply modern layout patterns (flexbox, grid, Bento) based on your layout needs
  6. 6.Implement typography system with font stacks and type scales from the guide
  7. 7.Extract repeated utility combinations into components when used 3+ times
  8. 8.Validate against anti-patterns (arbitrary values, !important, @apply overuse)

Use cases

Good for
  • Migrating from Tailwind v3 to v4 and adopting CSS-first configuration
  • Building responsive components using container queries instead of viewport breakpoints
  • Designing color systems with semantic tokens and OKLCH color format
  • Creating reusable component libraries with consistent spacing and typography scales
  • Implementing dark mode with class-based or system-preference strategies
Who it's for
  • Frontend developers building with Tailwind CSS v4
  • UI/UX designers implementing design systems
  • Full-stack developers configuring utility-first CSS frameworks
  • Teams migrating from Tailwind v3 to v4
  • Component library maintainers using design tokens

tailwind-patterns FAQ

What's the main difference between Tailwind v3 and v4?

v4 uses CSS-first configuration with @theme directives instead of tailwind.config.js, includes the Oxide engine (10x faster), and exposes all tokens as CSS variables. The PostCSS plugin is replaced with native CSS features.

When should I use container queries instead of viewport breakpoints?

Use container queries (@container) for component-level responsive design that works independently of viewport size. Use viewport breakpoints (md:, lg:) for page-level layouts that respond to screen width.

How do I define semantic color tokens in v4?

Use the @theme directive in CSS with semantic names like --color-primary, --color-surface, etc., preferably in OKLCH format for perceptual uniformity. These are automatically exposed as CSS variables.

Should I use @apply in Tailwind v4?

@apply still works but is discouraged in v4. Extract repeated utility combinations into React/Vue components instead, or use design tokens for reusable values.

What's the recommended approach for dark mode?

Choose based on your needs: use 'class' method for manual theme switching with .dark class, 'media' for system preference detection, or 'selector' for custom theming logic.

Full instructions (SKILL.md)

Source of truth, from sickn33/agentic-awesome-skills.


name: tailwind-patterns description: "Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture." risk: none source: community date_added: "2026-02-27"

Tailwind CSS Patterns (v4 - 2025)

Modern utility-first CSS with CSS-native configuration.

When to Use

Use this skill when configuring Tailwind v4, using CSS-first theme and design tokens, or implementing container queries and modern Tailwind patterns.


1. Tailwind v4 Architecture

What Changed from v3

v3 (Legacy)v4 (Current)
tailwind.config.jsCSS-based @theme directive
PostCSS pluginOxide engine (10x faster)
JIT modeNative, always-on
Plugin systemCSS-native features
@apply directiveStill works, discouraged

v4 Core Concepts

ConceptDescription
CSS-firstConfiguration in CSS, not JavaScript
Oxide EngineRust-based compiler, much faster
Native NestingCSS nesting without PostCSS
CSS VariablesAll tokens exposed as --* vars

2. CSS-Based Configuration

Theme Definition

@theme {
  /* Colors - use semantic names */
  --color-primary: oklch(0.7 0.15 250);
  --color-surface: oklch(0.98 0 0);
  --color-surface-dark: oklch(0.15 0 0);
  
  /* Spacing scale */
  --spacing-xs: 0.25rem;
  --spacing-sm: 0.5rem;
  --spacing-md: 1rem;
  --spacing-lg: 2rem;
  
  /* Typography */
  --font-sans: 'Inter', system-ui, sans-serif;
  --font-mono: 'JetBrains Mono', monospace;
}

When to Extend vs Override

ActionUse When
ExtendAdding new values alongside defaults
OverrideReplacing default scale entirely
Semantic tokensProject-specific naming (primary, surface)

3. Container Queries (v4 Native)

Breakpoint vs Container

TypeResponds To
Breakpoint (md:)Viewport width
Container (@container)Parent element width

Container Query Usage

PatternClasses
Define container@container on parent
Container breakpoint@sm:, @md:, @lg: on children
Named containers@container/card for specificity

When to Use

ScenarioUse
Page-level layoutsViewport breakpoints
Component-level responsiveContainer queries
Reusable componentsContainer queries (context-independent)

4. Responsive Design

Breakpoint System

PrefixMin WidthTarget
(none)0pxMobile-first base
sm:640pxLarge phone / small tablet
md:768pxTablet
lg:1024pxLaptop
xl:1280pxDesktop
2xl:1536pxLarge desktop

Mobile-First Principle

  1. Write mobile styles first (no prefix)
  2. Add larger screen overrides with prefixes
  3. Example: w-full md:w-1/2 lg:w-1/3

5. Dark Mode

Configuration Strategies

MethodBehaviorUse When
class.dark class togglesManual theme switcher
mediaFollows system preferenceNo user control
selectorCustom selector (v4)Complex theming

Dark Mode Pattern

ElementLightDark
Backgroundbg-whitedark:bg-zinc-900
Texttext-zinc-900dark:text-zinc-100
Bordersborder-zinc-200dark:border-zinc-700

6. Modern Layout Patterns

Flexbox Patterns

PatternClasses
Center (both axes)flex items-center justify-center
Vertical stackflex flex-col gap-4
Horizontal rowflex gap-4
Space betweenflex justify-between items-center
Wrap gridflex flex-wrap gap-4

Grid Patterns

PatternClasses
Auto-fit responsivegrid grid-cols-[repeat(auto-fit,minmax(250px,1fr))]
Asymmetric (Bento)grid grid-cols-3 grid-rows-2 with spans
Sidebar layoutgrid grid-cols-[auto_1fr]

Note: Prefer asymmetric/Bento layouts over symmetric 3-column grids.


7. Modern Color System

OKLCH vs RGB/HSL

FormatAdvantage
OKLCHPerceptually uniform, better for design
HSLIntuitive hue/saturation
RGBLegacy compatibility

Color Token Architecture

LayerExamplePurpose
Primitive--blue-500Raw color values
Semantic--color-primaryPurpose-based naming
Component--button-bgComponent-specific

8. Typography System

Font Stack Pattern

TypeRecommended
Sans'Inter', 'SF Pro', system-ui, sans-serif
Mono'JetBrains Mono', 'Fira Code', monospace
Display'Outfit', 'Poppins', sans-serif

Type Scale

ClassSizeUse
text-xs0.75remLabels, captions
text-sm0.875remSecondary text
text-base1remBody text
text-lg1.125remLead text
text-xl+1.25rem+Headings

9. Animation & Transitions

Built-in Animations

ClassEffect
animate-spinContinuous rotation
animate-pingAttention pulse
animate-pulseSubtle opacity pulse
animate-bounceBouncing effect

Transition Patterns

PatternClasses
All propertiestransition-all duration-200
Specifictransition-colors duration-150
With easingease-out or ease-in-out
Hover effecthover:scale-105 transition-transform

10. Component Extraction

When to Extract

SignalAction
Same class combo 3+ timesExtract component
Complex state variantsExtract component
Design system elementExtract + document

Extraction Methods

MethodUse When
React/Vue componentDynamic, JS needed
@apply in CSSStatic, no JS needed
Design tokensReusable values

11. Anti-Patterns

Don'tDo
Arbitrary values everywhereUse design system scale
!importantFix specificity properly
Inline style=Use utilities
Duplicate long class listsExtract component
Mix v3 config with v4Migrate fully to CSS-first
Use @apply heavilyPrefer components

12. Performance Principles

PrincipleImplementation
Purge unusedAutomatic in v4
Avoid dynamismNo template string classes
Use OxideDefault in v4, 10x faster
Cache buildsCI/CD caching

Remember: Tailwind v4 is CSS-first. Embrace CSS variables, container queries, and native features. The config file is now optional.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.