nextjs-shadcn-builder

Analyze frontend codebases and generate Next.js + shadcn/ui migration plans.

Updated Jan 9, 2026
One-click install
npx skills add https://github.com/SKANL/saas-abogados-nextjs --skill nextjs-shadcn-builder-skanl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nextjs-shadcn-builder
Source: https://github.com/SKANL/saas-abogados-nextjs/tree/main/.agents/skills/nextjs-shadcn-builder
Command: npx skills add https://github.com/SKANL/saas-abogados-nextjs --skill nextjs-shadcn-builder-skanl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill enables teams to bootstrap production-ready Next.js + shadcn/ui apps or migrate existing frontends (React, Vue, Angular, or vanilla JS) with a design system that uses CSS variables and consistent tokens.

Core Features & Use Cases

  • Automated migration planning and MCP-driven component mapping to shadcn/ui equivalents.
  • Phase-driven migration workflows with clear deliverables and design-token enforcement (OKLCH colors, CSS variables).
  • Guidance and code scaffolding for new apps, standardizing component libraries, and adopting shadcn/ui across teams.

Quick Start

  • Initialize a new project: bash ./scripts/init-nextjs-shadcn.sh my-app
  • Analyze your existing frontend: python ./scripts/analyze-codebase.py /path/to/your/codebase
  • Generate a migration plan: python ./scripts/generate-migration-plan.py

Frequently Asked Questions about nextjs-shadcn-builder

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

FAQPage Schema
How do I migrate an existing React or Vue frontend to Next.js and shadcn/ui?

Migrate frontends by analyzing the codebase to generate a migration plan with MCP-driven component mappings and design-token alignment for Next.js and shadcn/ui. It enforces OKLCH colors and CSS variables across React, Vue, Angular, and vanilla JS projects.

What is MCP-driven component mapping for design system migration?

MCP-driven component mapping matches existing frontend elements to shadcn/ui equivalents while enforcing design-token alignment. It provides structured outputs for CSS variables and OKLCH colors to standardize component libraries during migration.

Can I use this to scaffold a new Next.js app with a standardized shadcn/ui component library?

Yes, you can bootstrap production-ready Next.js apps with a standardized shadcn/ui component library. The skill provides initialization scripts and code scaffolding to enforce consistent design tokens and CSS variables across new projects.

Does the migration plan support Angular and vanilla JS codebases?

Yes, the migration plan supports Angular and vanilla JS codebases alongside React and Vue. It analyzes these frontend architectures to produce phase-driven workflows with clear deliverables and shadcn/ui component mappings.

How do I generate a design-token alignment plan for OKLCH colors and CSS variables?

Generate a design-token alignment plan by running the codebase analysis script to evaluate your frontend. It produces structured token documentation mapping existing styles to shadcn/ui OKLCH colors and CSS variables.