What problem does it solve? Adding user authentication to a Next.js application involves choosing between providers, configuring middleware, protecting routes, and keeping up with breaking SDK changes. This Skill provides concrete, current integration guidance for Clerk, Descope, and Auth0 so you avoid deprecated patterns and misconfigured middleware. ## Core Features & Use Cases - Provider Integration Guides: Step-by-step setup for Clerk (native Vercel Marketplace), Descope, and Auth0, including SDK installation, provider components, and middleware configuration. - Route Protection Patterns: Covers createRouteMatcher, auth.protect(), API route guards, and sign-in/sign-up page setup with environment variables. - Migration & Validation Rules: Detects legacy next-auth v4 patterns, manual JWT handling with jsonwebtoken, hand-rolled Vercel OAuth, and Clerk Core 3 breaking changes, then recommends modern replacements. - Use Case: You are building a Next.js dashboard on Vercel and need login. This Skill walks you through installing Clerk from the Marketplace, wiring clerkMiddleware, and protecting /dashboard routes in minutes. ## Quick Start Ask the assistant to add Clerk authentication with protected dashboard routes to your Next.js app.