tailwind-design-system-v4

Build scalable, responsive, and accessible design systems with Tailwind CSS v4 — design tokens, theme configuration, reusable React UI components, and migration from v3.

54 stars

Best use case

tailwind-design-system-v4 is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Build scalable, responsive, and accessible design systems with Tailwind CSS v4 — design tokens, theme configuration, reusable React UI components, and migration from v3.

Teams using tailwind-design-system-v4 should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/tailwind-design-system-v4/SKILL.md --create-dirs "https://raw.githubusercontent.com/bidewio/better-openclaw/main/skills/tailwind-design-system-v4/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/tailwind-design-system-v4/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How tailwind-design-system-v4 Compares

Feature / Agenttailwind-design-system-v4Standard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Build scalable, responsive, and accessible design systems with Tailwind CSS v4 — design tokens, theme configuration, reusable React UI components, and migration from v3.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Tailwind Design System v4 Skill

## When to use
- Building a design system with Tailwind CSS v4
- Migrating from Tailwind v3 to v4
- Creating reusable, accessible React components with Tailwind

## What's new in v4
- **CSS-first configuration**: No more `tailwind.config.js` — use CSS `@theme` directive
- **Native CSS variables**: All design tokens are CSS custom properties
- **Lightning CSS**: Built-in CSS processing, no PostCSS needed
- **Automatic content detection**: No `content` config required

## Theme configuration (v4)
```css
@import "tailwindcss";

@theme {
  --color-primary-50: #eff6ff;
  --color-primary-500: #3b82f6;
  --color-primary-900: #1e3a5f;
  --font-sans: "Inter", system-ui, sans-serif;
  --spacing-gutter: 1.5rem;
  --radius-card: 0.75rem;
}
```

## Component pattern (React + v4)
```tsx
function Button({ variant = "primary", size = "md", children, ...props }) {
  const base = "inline-flex items-center justify-center font-medium rounded-card transition-colors";
  const variants = {
    primary: "bg-primary-500 text-white hover:bg-primary-600",
    secondary: "bg-gray-100 text-gray-900 hover:bg-gray-200",
    ghost: "text-gray-600 hover:bg-gray-100",
  };
  const sizes = { sm: "px-3 py-1.5 text-sm", md: "px-4 py-2 text-base", lg: "px-6 py-3 text-lg" };
  return <button className={`${base} ${variants[variant]} ${sizes[size]}`} {...props}>{children}</button>;
}
```

## Migration from v3
- Replace `tailwind.config.js` theme with `@theme` in CSS
- Remove PostCSS config (Lightning CSS handles it)
- Update `content` paths (auto-detection in v4)
- Replace `@apply` with CSS custom properties where possible

## Tips for AI Agents
- Always confirm the Tailwind version before generating code.
- Use CSS variables for tokens instead of config-based approaches in v4.
- Test with `npx @tailwindcss/upgrade` for automated migration.

Related Skills

web-design-reviewer

54
from bidewio/better-openclaw

Inspect web interfaces for layout, responsive, accessibility, and visual issues, then apply targeted source code fixes and re-verify results.

ui-design-system

54
from bidewio/better-openclaw

Create and maintain scalable UI design systems with design tokens, responsive rules, accessibility standards, component libraries, and developer handoff documentation.

tailwindcss-style

54
from bidewio/better-openclaw

Ship beautiful sites fast with Tailwind CSS — responsive/state variants, safe dynamic class patterns, component extraction, and conventions for maintainable utility-first styling.

system-info

54
from bidewio/better-openclaw

Monitor system resources including CPU, memory, disk, and network usage.

responsive-design

54
from bidewio/better-openclaw

Master modern responsive design techniques — container queries, fluid typography with clamp(), CSS Grid, Flexbox patterns, and mobile-first strategies for adaptive interfaces.

pricing-page-design

54
from bidewio/better-openclaw

Design high-conversion SaaS pricing pages with plan structures, comparison patterns, conversion strategies, copy templates, SEO/AEO checklists, and layout types (3-card, slider, persona split, enterprise).

landing-page-design

54
from bidewio/better-openclaw

Design high-conversion landing pages with structure, section order, layout types (classic hero, long-form, minimal, comparison), conversion strategies, SEO/AEO guidance, and copywriting templates.

interaction-design

54
from bidewio/better-openclaw

Design and implement purposeful UI motion, microinteractions, and feedback patterns to enhance usability and user delight — hover effects, transitions, loading states, and gesture responses.

frontend-distinctive-design

54
from bidewio/better-openclaw

Create distinctive, production-grade frontend interfaces with bold, cohesive aesthetics and refined implementation — visual identity, typography systems, color palettes, and layout composition.

canvas-design

54
from bidewio/better-openclaw

Create original visual design philosophies and express them as meticulously crafted, museum-quality PNG or PDF art with minimal text — generative art, data visualization, and abstract compositions.

web-design-guidelines

54
from bidewio/better-openclaw

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

youtube-growth

54
from bidewio/better-openclaw

Act as an expert YouTube Strategy Consultant. Apply the Creator Unlock N.I.C.E.R. Framework for conducting channel audits, niche validation, and data-backed video ideation/thumbnail generation.