What problem does it solve? Migrating an ASP.NET MVC solution to Node.js + React requires deciding where controllers, Razor views, models, and services belong in a new repository. This Skill provides a canonical monorepo layout (apps/web, apps/api, packages/shared) with ready-to-use configuration templates so teams avoid ad-hoc folder decisions. ## Core Features & Use Cases - Canonical Monorepo Layout: Defines apps/web (Vite + React 18 + TypeScript + Tailwind + shadcn/ui), apps/api (Node.js 20 TypeScript base), and packages/shared (zod schemas and generated OpenAPI types). - ASP.NET MVC Mapping Table: Maps .sln files, Controllers, Views, ViewModels, Web.config, and Global.asax to their Node.js/React equivalents. - Ready-to-Use Templates: Ships pnpm-workspace.yaml, tsconfig chains, ESLint/Prettier configs, Dockerfile, Vite config, Tailwind config, and starter React source files. - Use Case: During Phase 1 of a migration, scaffold the target repository by copying the templates, then run pnpm install and pnpm dev to start both the web and API workspaces. ## Quick Start Ask the AI to scaffold the migration monorepo using the react-project-structure skill with apps/web, apps/api, and packages/shared workspaces.