- Home
- Skills
- Frontend & Web Apps
- tailwind v4 shadcn library builder
tailwind v4 shadcn library builder
Builds WCAG-compliant Tailwind v4 and shadcn/ui libraries with automated contrast checks and Storybook stories.
$9
Works with the AI Agents you already use
tailwind v4 shadcn library builder
Example session with this skill installed
Migrate my tailwind.config.js to v4 and build a Button, Input, and Checkbox for a brand with #F5A623 primary and Inter font. Verify contrast and write Storybook 10 stories.
- Read your context and instructions
- Compiled the tailwind v4 shadcn
Detected Vite + React project with Tailwind 3.4. The migration to Tailwind v4 is complete, and 3 hardened components have been generated with Storybook 10 stories.
Token Migration Map
| Source | v4 Variable | Utility | Note |
|---|---|---|---|
theme.colors.brand | --color-brand | bg-brand | Mapped to #F5A623 |
theme.fontFamily.sans | --font-inter | font-inter | Primary font |
Contrast Verification
| Element | Background | Foreground | Ratio | Result |
|---|---|---|---|---|
| Button (Primary) | #F5A623 | #FFFFFF | 2.03:1 | ❌ FAIL |
| Button (Primary) | #F5A623 | #1C1917 | 12.8:1 | ✅ FIXED |
Deviations from brief:
- Brief asked for white text on #F5A623. Changed to ink #1C1917 to meet 4.5:1 requirement.
Files Generated
.
├── src/index.css
├── components/ui/
│ ├── button.tsx
│ ├── input.tsx
│ └── checkbox.tsx
└── stories/
├── Button.stories.tsx
├── Input.stories.tsx
└── Checkbox.stories.tsx
/* src/index.css */
@import "tailwindcss";
@theme static {
--color-brand: #f5a623;
--font-inter: "Inter", sans-serif;
}
:root {
--background: #ffffff;
--foreground: #1c1917;
--primary: var(--brand);
--primary-foreground: #1c1917;
/* ... other shadcn variables */
}
Accessibility Decisions
- Button: Added
focus-visible:ring-2to ensure keyboard navigation visibility. - Checkbox: Increased hit area to 24px via transparent padding to meet SC 2.5.8.
- Input: Linked
FieldErrorto input viaaria-describedbyfor screen reader error announcements.
Verification log:
npx @tailwindcss/upgrade: Exit 0node scripts/check-contrast.mjs: Found 1 failure, applied fix.axe-core: 0 violations in 6 stories (Light/Dark).
Next steps
- Run
npm run storybookto review the new Foundations/Tokens story. - Confirm the #1C1917 ink text color with the design team.
- Commit the
@tailwindcss/upgradediff to a new branch.
Connects securely to your tools. The creator never sees your data.
About this skill
Building a cohesive, accessible UI kit is a slog of manual checks and configuration drift. This skill automates the creation of a design system using Tailwind CSS v4 and shadcn/ui, ensuring every component meets WCAG 2.2 AA standards from the first render. It moves your design tokens into the v4 @theme layer and hardens components against common accessibility failures.
What it does
- Token migration maps Tailwind v3 configs or JSON design tokens into Tailwind v4
@theme staticand semantic variables. - Automated contrast checks runs a bundled Node script to verify foreground/background pairs against WCAG AA 4.5:1 requirements.
- Component hardening applies
focus-visiblerings, 24px minimum hit targets, andaria-invalidstates to standard shadcn primitives. - Storybook 10 generation writes CSF3 stories with automated a11y tests and
playfunction keyboard interaction checks. - Reduced motion support injects
prefers-reduced-motionlogic globally to handle layout shifts and animations.
How it works
- Analyze your
package.jsonand CSS to detect existing Tailwind, shadcn, and Storybook versions. - Execute the
npx @tailwindcss/upgradetool and generate the new v4@themevariable mapping. - Verify contrast ratios using the
check-contrast.mjsscript and log any necessary brand color deviations. - Provision components via the shadcn CLI and wrap them in Storybook stories for visual and automated testing.
Frameworks & tools
React, Next.js, Vite, Tailwind CSS v4, shadcn/ui, Radix UI, Storybook 10, and Axe-core.
Why this beats prompting it yourself
Standard LLMs often hallucinate Tailwind v4 syntax or suggest outdated accessibility patterns. This skill uses a strict multi-step verification loop, including a dedicated contrast script and Storybook play tests, to catch violations that are invisible in static code.
Use cases
- Migrating a legacy design system from Tailwind v3 to the v4 CSS-first theme engine.
- Building a greenfield accessible UI library for a client with strict WCAG compliance needs.
- Scaffolding a complete shadcn component suite with Storybook documentation in minutes.
Known limitations
Does not support Vue or Svelte shadcn ports. Requires Node 20+ for the Tailwind upgrade utility and contrast script. Storybook stories for Next.js Server Components require manual mocking.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Frontend & Web Apps.
React only. Requires Node 20+ for v4 upgrade scripts. Manual mocking needed for Next.js Server Components in Storybook. No Figma-to-code sync.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 13 days ago
- Software
- shadcn
Node.jsstorybook@tailwindcss/upgradevitest