Agent skill · design visual · pedronauck
tailwindcss
Style components with Tailwind CSS v4 and project tokens. Excludes plain CSS, CSS-in-JS, and other utility frameworks.
Why this skill is useful
Provides specific conventions and semantic design tokens for Tailwind CSS v4 that enhance styling consistency and mobile-first design practices.
What it needs
About 1k tokens when loaded. Last updated 2026-08-01. 564 stars on the source repository.
What this skill does
Tailwind CSS v4 Prefer utilities for component styling. CSS still owns theme tokens, base rules, and styles that utilities do not express clearly. Use the installed Tailwind version and existing design system. Use semantic tokens for theme-aware colors, borders, and states. Use names from the project's token source and design documentation; do not assume a universal shadcn vocabulary. Keep class names complete and statically discoverable. Use lookup maps instead of interpolated fragments such as bg-${color}-500. Group long classes for readability; no character-count gate. Use the project's cn/merge helper when composing variants or accepting overriding className values. Resolve specificity through the style design and class merging, avoiding !important. Use @apply only where the repository permits it. Build responsive layouts from content needs, preserve visible keyboard focus, and select supported v4 utilities rather than copying older idioms. Validate through the repository's owning gates. Use its existing root/package commands and reuse valid evidence; styling does not add a separate lint/typecheck ritual. Read references/patterns.md for the utility or variant being changed. Its token names are examples; use the actual theme inventory.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills pedronauck/tailwindcss