tailwind design system

Design Community

Skill notes

When to Use This Skill

Creating a component library with Tailwind v4 Implementing design tokens and theming with CSS-first configuration Building responsive and accessible components Standardizing UI patterns across a codebase Migrating from Tailwind v3 to v4

Key v4 Changes

v3 Pattern · v4 Pattern tailwind.config.ts · @theme in CSS @tailwind base/components/utilities · @import "tailwindcss" darkMode: "class" · @custom-variant dark (&:where(.dark, .dark *)) theme.extend.colors · @theme { --color-*: value }

Detailed patterns and worked examples

Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Design
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@wshobson · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview tailwind-design-system.preview
# Detailed patterns and worked examples

Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.