tailwind v4 shadcn library builder

    1

    Builds WCAG-compliant Tailwind v4 and shadcn/ui libraries with automated contrast checks and Storybook stories.

    $9

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    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

    Sourcev4 VariableUtilityNote
    theme.colors.brand--color-brandbg-brandMapped to #F5A623
    theme.fontFamily.sans--font-interfont-interPrimary font

    Contrast Verification

    ElementBackgroundForegroundRatioResult
    Button (Primary)#F5A623#FFFFFF2.03:1❌ FAIL
    Button (Primary)#F5A623#1C191712.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-2 to ensure keyboard navigation visibility.
    • Checkbox: Increased hit area to 24px via transparent padding to meet SC 2.5.8.
    • Input: Linked FieldError to input via aria-describedby for screen reader error announcements.

    Verification log:

    • npx @tailwindcss/upgrade: Exit 0
    • node scripts/check-contrast.mjs: Found 1 failure, applied fix.
    • axe-core: 0 violations in 6 stories (Light/Dark).

    Next steps

    1. Run npm run storybook to review the new Foundations/Tokens story.
    2. Confirm the #1C1917 ink text color with the design team.
    3. Commit the @tailwindcss/upgrade diff 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 static and 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-visible rings, 24px minimum hit targets, and aria-invalid states to standard shadcn primitives.
    • Storybook 10 generation writes CSF3 stories with automated a11y tests and play function keyboard interaction checks.
    • Reduced motion support injects prefers-reduced-motion logic globally to handle layout shifts and animations.

    How it works

    1. Analyze your package.json and CSS to detect existing Tailwind, shadcn, and Storybook versions.
    2. Execute the npx @tailwindcss/upgrade tool and generate the new v4 @theme variable mapping.
    3. Verify contrast ratios using the check-contrast.mjs script and log any necessary brand color deviations.
    4. 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. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 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
    shadcnNode.jsstorybook@tailwindcss/upgradevitest

    Permissions

    Read Files
    Write Files
    Listed13 days ago

    What's inside

    Frequently Asked Questions

    This skill automates the transition to Tailwind v4's CSS-first engine, specifically mapping your existing design tokens to the new @theme layer while enforcing WCAG 2.2 AA accessibility standards across all shadcn components.

    Yes, the skill includes a dedicated contrast verification script that checks your theme's foreground/background pairs against a 4.5:1 ratio, flagging any brand colors that fail compliance.

    The skill is designed for React-based environments, specifically supporting Next.js and Vite projects using Node 20 or higher.

    You receive the full automation workflow for Tailwind v4 migration, a hardened shadcn/ui component suite, and Storybook 10 documentation with pre-configured interaction tests.

    While the skill scaffolds Storybook stories for most components, Next.js Server Components (RSC) will require manual mocking within the Storybook environment to function correctly.

    This skill uses a strict multi-step verification loop that runs external scripts to catch accessibility violations that standard LLMs often miss or hallucinate.

    New in Frontend & Web Apps