Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
boise-state-development avatar

Tailwind Ui

  • 25 installs
  • 15 repo stars
  • Updated August 3, 2026
  • boise-state-development/agentcore-public-stack

tailwind-ui is a Claude Code skill that applies Tailwind CSS v4.1 best practices with WCAG 2.1 AA accessibility, theming, and dark mode support.

About

tailwind-ui is a Claude Code skill for Tailwind CSS v4.1 development with WCAG 2.1 AA accessibility, theming, and dark mode support. It provides a quick reference of v4.1 breaking changes, deprecated-to-replacement utility mappings, essential patterns, and pointers to reference files on migration, accessibility, theming, and components. A developer uses it when styling components or building accessible UI patterns. It complements the angular-best-practices skill for Angular frontends.

  • Applies Tailwind CSS v4.1 best practices with WCAG 2.1 AA accessibility baked in
  • Maps deprecated v4 utilities to their current replacements
  • Covers theming, dark mode, and accessible component patterns via reference files

Tailwind Ui by the numbers

  • 25 all-time installs (skills.sh)
  • Ranked #1,503 of 2,245 Frontend Development skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
At a glance

tailwind-ui capabilities & compatibility

Capabilities
style with tailwind · build accessible components · configure dark mode · apply theming
Use cases
frontend · ui design
Runs
Runs locally
Pricing
Free
From the docs

What tailwind-ui says it does

Tailwind CSS v4.1 best practices with WCAG 2.1 AA accessibility, theming, and dark mode support.
SKILL.md
Tailwind CSS v4.1 development with accessibility and theming baked in.
SKILL.md
**Never use @apply** — Use CSS variables or framework components
SKILL.md
npx skills add https://github.com/boise-state-development/agentcore-public-stack --skill tailwind-ui

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs25
repo stars15
Last updatedAugust 3, 2026
Repositoryboise-state-development/agentcore-public-stack

What it does

Style components with Tailwind CSS v4.1 following accessibility, theming, and dark mode best practices.

Who is it for?

Developers styling components or building accessible UI patterns with Tailwind CSS v4.1

Skip if: Using deprecated Tailwind utilities like bg-opacity-* or @apply, which the skill forbids

When should I use this skill?

working with Tailwind CSS, styling components, or building accessible buttons, forms, cards, or navigation

What you get

Components use current v4.1 utilities with proper contrast, focus states, theming, and dark mode.

  • accessible Tailwind components
  • themed light and dark mode styles
  • v4.1-compliant utility usage

By the numbers

  • Tailwind CSS v4.1
  • WCAG 2.1 AA
  • 4 reference files (v4-migration, accessibility, theming, components)

Files

SKILL.mdMarkdownGitHub ↗

Tailwind UI Skill

Tailwind CSS v4.1 development with accessibility and theming baked in.

Quick Reference

v4.1 Critical Changes

Never use deprecated utilities — always use replacements:

DeprecatedReplacement
bg-opacity-*bg-black/50 (opacity modifier)
bg-gradient-*bg-linear-*
shadow-smshadow-xs
shadowshadow-sm
rounded-smrounded-xs
roundedrounded-sm
ringring-3
outline-noneoutline-hidden
leading-*Use text-base/7 line-height modifiers
flex-shrink-* / flex-grow-*shrink-* / grow-*
space-x-* in flex/gridUse gap-* instead

Essential Patterns

<!-- Gap over space utilities -->
<div class="flex gap-4">...</div>

<!-- Opacity modifiers -->
<div class="bg-primary-500/60">...</div>

<!-- Line height modifiers -->
<p class="text-base/7">...</p>

<!-- Dynamic viewport height (mobile-safe) -->
<div class="min-h-dvh">...</div>

<!-- Size utility for equal dimensions -->
<div class="size-12">...</div>

Reference Files

Load these based on the task:

  • [references/v4-migration.md](references/v4-migration.md) — Full v4.1 breaking changes, upgrade process, new features
  • [references/accessibility.md](references/accessibility.md) — WCAG 2.1 AA patterns: contrast, focus, screen readers
  • [references/theming.md](references/theming.md) — @theme setup, CSS variables, light/dark mode
  • [references/components.md](references/components.md) — Accessible component patterns (buttons, forms, cards, nav)

Theme Asset

  • [assets/theme-starter.css](assets/theme-starter.css) — Starter @theme with primary/secondary/tertiary color scales

Core Principles

1. Use Tailwind's scale — Avoid arbitrary values like ml-[16px]; use ml-4 2. Never use @apply — Use CSS variables or framework components 3. Gap over margins — Use gap-* in flex/grid, not space-* or child margins 4. Test both modes — Always verify light AND dark mode appearance 5. Accessibility first — Every interactive element needs visible focus states and proper contrast

Related skills

FAQ

What replaces bg-opacity-* in Tailwind v4.1?

Use the opacity modifier syntax like bg-black/50 instead of bg-opacity-*.

Should I use @apply?

No, the skill says never use @apply; use CSS variables or framework components instead.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.