What problem does it solve? Adding user authentication to a Next.js application involves choosing a provider, configuring middleware, protecting routes, and handling sign-in flows, and mistakes in any of these steps leave routes exposed or sessions broken. ## Core Features & Use Cases - Provider Setup Guidance: Step-by-step integration for Clerk (native Vercel Marketplace), Descope, and Auth0, including SDK installation, environment variables, and provider components. - Middleware and Route Protection: Patterns for clerkMiddleware, createRouteMatcher, Descope authMiddleware, and Auth0 middleware to secure pages and API routes. - Migration and Validation Rules: Detects legacy next-auth v4, manual JWT handling, bcrypt password hashing, and hand-rolled Vercel OAuth, then directs to managed auth with Clerk Core 3 breaking-change guidance. - Use Case: You need login on your Next.js dashboard. The Skill provisions Clerk via the Vercel Marketplace, wires up middleware protection for /dashboard routes, and adds pre-built SignIn and SignUp pages. ## Quick Start Add Clerk authentication with protected dashboard routes and sign-in pages to my Next.js app.