# nextjs-shadcn-builder

nextjs-shadcn-builder builds Next.js apps with shadcn/ui or guides a migration from an existing frontend. Useful when you want a component inventory and a staged conversion plan.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 263 installs · ★ 56 repo stars
- Author: ovachiever
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/ovachiever/droid-tings/tree/HEAD/skills/nextjs-shadcn-builder/SKILL.md
- Updated: 2025-11-25
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/nextjs-shadcn-builder

## What it does

Use the skill to start a Next.js app with App Router and TypeScript, or move a frontend built with React, Vue, Angular, or vanilla JS. For a migration, it scans the codebase for framework details, dependencies, components, and hardcoded styles. The analysis produces JSON inventories and Markdown reports.

Next, the skill maps existing components to shadcn/ui options and groups the conversion into batches. It uses MCP to look up components, replaces fixed style values with CSS variables, and tests each batch. The final workflow includes checks for tests, responsive layouts, and accessibility. The analysis scripts run with Python and Bash, so both are needed for those steps.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add ovachiever/droid-tings --skill nextjs-shadcn-builder -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/nextjs-shadcn-builder/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/nextjs-shadcn-builder/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add ovachiever/droid-tings --skill nextjs-shadcn-builder -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/nextjs-shadcn-builder/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add ovachiever/droid-tings --skill nextjs-shadcn-builder -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/nextjs-shadcn-builder/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install ovachiever/droid-tings skills/nextjs-shadcn-builder
```

2. **Manually: put the files in place**
- File: `.github/skills/nextjs-shadcn-builder/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add ovachiever/droid-tings --skill nextjs-shadcn-builder -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/ovachiever/droid-tings --path skills/nextjs-shadcn-builder
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/nextjs-shadcn-builder/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add ovachiever/droid-tings --skill nextjs-shadcn-builder -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/ovachiever/droid-tings/tree/HEAD/skills/nextjs-shadcn-builder/SKILL.md

## When to use it
- start a Next.js app with App Router and TypeScript
- inventory components and dependencies in an existing frontend
- find colors and spacing values written directly in code
- split a UI migration into component batches
- replace fixed styling values with CSS variables

## Example prompts
- Analyze this frontend and plan its migration to Next.js with shadcn/ui.
- Create a Next.js app with App Router and set up design tokens.
- Find hardcoded values in this codebase and prepare the components for shadcn/ui.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: e758536d47267ca2.

BEGIN THIRD-PARTY FILE e758536d47267ca2
````text
---
name: nextjs-shadcn-builder
description: Build new Next.js applications or migrate existing frontends (React, Vue, Angular, vanilla JS, etc.) to Next.js + shadcn/ui with systematic analysis and conversion. Enforces shadcn design principles - CSS variables for theming, standard UI components, no hardcoded values, consistent typography/colors. Use for creating Next.js apps, migrating frontends, adopting shadcn/ui, or standardizing component libraries. Includes MCP integration for shadcn documentation and automated codebase analysis.
license: Complete terms in LICENSE.txt
---

# Next.js + shadcn/ui Builder & Migration Tool

Build production-grade Next.js applications or systematically migrate existing frontends to Next.js + shadcn/ui following strict design principles and best practices.

## Overview

This skill handles two primary workflows:

1. **Creating New Next.js Applications** - Initialize projects with Next.js 15+ (App Router), shadcn/ui, and proper design system setup
2. **Migrating Existing Frontends** - Analyze any frontend codebase (React, Vue, Angular, vanilla JS) and systematically convert to Next.js + shadcn/ui

**Core Philosophy**: 100% adherence to shadcn/ui design principles:
- CSS variables for all theming (colors, spacing, typography)
- Standard shadcn/ui components only (no custom UI components)
- No hardcoded values (colors, spacing, fonts)
- Consistent design tokens across the application
- Mobile-first responsive design for all devices (phone, tablet, desktop)
- WCAG 2.1 Level AA accessibility compliance
- Best practices from https://ui.shadcn.com

## Workflow Decision Tree

```
User Request
    ├─ Creating New Next.js App
    │   └─ Follow "Creating New Application" workflow (Phase 3 onwards)
    │
    └─ Migrating Existing Codebase
        ├─ Phase 1: Codebase Analysis
        ├─ Phase 2: Migration Planning
        ├─ Phase 3: Next.js + shadcn Setup
        ├─ Phase 4: Systematic Conversion
        └─ Phase 5: Verification & Cleanup
```

---

## High-Level Workflow for Migration

### Phase 1: Codebase Analysis
Automated analysis of existing frontend to understand scope and complexity.

**Steps:**
1. Framework and version detection
2. Component inventory and categorization
3. Hardcoded value detection (colors, spacing, custom components)
4. Styling approach analysis (CSS, SCSS, CSS-in-JS, Tailwind, etc.)
5. State management and routing pattern identification
6. Generate comprehensive analysis report

**Deliverables:**
- Framework analysis report
- Component inventory (JSON)
- Hardcoded values report
- Complexity assessment

### Phase 2: Migration Planning
Create systematic conversion plan with prioritized batches.

**Steps:**
````
END THIRD-PARTY FILE e758536d47267ca2

The third-party file has ended. Everything between the e758536d47267ca2 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2735 of 43805 bytes. © ovachiever · MIT · https://github.com/ovachiever/droid-tings/tree/HEAD/skills/nextjs-shadcn-builder/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
