clerk-nextjs-skills

Clerk authentication in Next.js 16 App Router uses proxy.ts middleware for secure request handling. Install @clerk/nextjs, create a proxy.ts file in your app directory, configure environment variables (NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY and CLERK_SECRET_KEY), wrap your app with ClerkProvider, and start your dev server. The Skill automates these steps end to end.

Yes, this Skill provides zero-diff migration guidance from middleware.ts to proxy.ts-based Clerk middleware. The migration preserves your existing authentication logic while adopting Next.js 16's proxy.ts pattern for cleaner route protection and environment validation.

Yes, Clerk integrates with MCP servers via @vercel/mcp-adapter and @clerk/mcp-tools for secure tool invocation and OAuth metadata handling. This Skill sets up patterns for agents to safely call Clerk-protected APIs and server actions with proper authentication context.

You need NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY (public, safe to expose) and CLERK_SECRET_KEY (private, server-side only). This Skill validates both variables at startup and applies safe defaults to prevent authentication failures during development and production deployments.

Yes, Clerk secures routes, server actions, and protected APIs through proxy.ts middleware. This Skill demonstrates real-world patterns for wrapping server-side logic with Clerk authentication, ensuring only authorized requests reach your backend handlers.

Yes, this Skill is built for pnpm-based setup and provides startup environment validation tailored to pnpm workspaces. It ensures dependency installation and configuration steps work correctly with pnpm package management.