What problem does it solve? Setting up authentication from scratch is error-prone: wrong SDK packages, misplaced providers, missing middleware, and leaked secret keys are common mistakes. This Skill automates Clerk integration by detecting your framework, provisioning API keys via the Clerk CLI, and following the official quickstart for your stack. ## Core Features & Use Cases - CLI-driven provisioning: Uses clerk init, clerk link, and clerk env pull to install SDKs, write framework-specific env vars, and generate temporary development keys without requiring a Clerk account. - Framework detection and quickstart execution: Reads package.json to identify Next.js, React, Vue, Nuxt, Astro, Express, Fastify, Expo, and more, then follows the matching official quickstart. - Migration planning: Audits existing auth (NextAuth, Supabase, Firebase, Auth0) and plans user data migration via the Clerk Backend API with big-bang or trickle strategies. - Use Case: You scaffold a new Next.js SaaS app and ask the agent to add authentication. It runs clerk init --framework next, places ClerkProvider inside <body>, creates proxy.ts middleware, writes keys to .env.local, and applies the shadcn theme if components.json exists. ## Quick Start Ask the agent to add Clerk authentication to your project and it will detect the framework, provision keys, and wire up the SDK automatically.
