design-system

Bootstrap and audit a Tailwind v4 design system with shadcn components.

1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/Levezze/devkit --skill design-system-levezze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-system
Source: https://github.com/Levezze/devkit/tree/main/skills/design-system
Command: npx skills add https://github.com/Levezze/devkit --skill design-system-levezze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents design drift and fragmented UI styling by centralizing tokens, utilities, and component families into one auditable design system.

Core Features & Use Cases

  • Bootstrap a tokenized baseline: scaffolds a manifesto-style design language plus a token-driven globals.css (Tailwind v4 @theme inline + semantic tokens for typography, radii, elevation, and colors).
  • Unify Tailwind behavior: generates extendTailwindMerge configuration so custom semantic utilities compose safely (e.g., font-size and interactive utilities).
  • Standardize component patterns: centralizes shadcn primitives and builds a shared component family (e.g., ActionCard) with consistent hover/interactive recipes and slot-based composition.
  • Visual verification via mock catalog: creates /mock pages (including a theme token catalog) and a theme-preview area so users can validate look & feel without touching production pages.
  • Audit existing drift: detects missing/misaligned tokens, hover/utility inconsistencies, and documentation gaps, then produces an approval-gated fix workflow.

Quick Start

Use the design-system skill to bootstrap a centralized Tailwind v4 + shadcn design system for your Next.js app, writing the required tokens, utilities, components, and mock catalog to your repository.

Frequently Asked Questions about design-system

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent design drift in a Tailwind v4 and shadcn component library?

Preventing design drift in a Tailwind v4 and shadcn component library requires centralizing styling tokens, semantic utilities, and component families into an auditable system with interactive drift detection and mock catalog visual verification.

How do I bootstrap a centralized design system for a Next.js App Router project?

Bootstrapping a centralized design system for Next.js App Router scaffolds a tokenized `globals.css` using `@theme inline`, generates safe `extendTailwindMerge` class groups, and writes opinionated typography, radii, and shadows directly into your repository.

What is the best way to audit design token inconsistencies in a React UI?

The best way to audit design token inconsistencies in a React UI is to detect missing tokens, hover inconsistencies, and documentation gaps, then generate an approval-gated fix workflow that writes a `.design-system-audit.md` file without silent auto-fixes.

Can I use shadcn primitives with custom semantic utilities without class conflicts?

Yes, you can use shadcn primitives with custom semantic utilities without class conflicts by generating an `extendTailwindMerge` configuration that ensures custom semantic utilities like font-size and interactive states compose safely together.

How do I visually verify design tokens and shadcn components without touching production pages?

To visually verify design tokens and shadcn components without touching production pages, you can create static `/mock` routes with component-only rendering and a theme-preview area to validate look and feel.