What problem does it solve? Developers integrating Clerk authentication often don't know which SDK pattern, CLI command, or framework-specific approach applies to their project, leading to mismatched implementations across Next.js, React, Expo, and other platforms. ## Core Features & Use Cases - Task-Based Routing: Directs requests to 19 specialized skills covering setup, CLI operations, custom UI, organizations, billing, webhooks, and testing. - SDK Version Detection: Reads package.json to distinguish Core 2 (v5–v6) from current (v7+) Clerk SDKs and applies the correct patterns. - Framework Coverage: Provides guidance for Next.js, React, React Router, Vue, Nuxt, Astro, TanStack Start, Expo, Chrome Extensions, Swift, and Android. - Use Case: A developer asks how to add organization-based billing to a Next.js app; the router detects the SDK version and routes to clerk-orgs and clerk-billing with the correct API patterns. ## Quick Start Ask how to add Clerk authentication to your framework of choice and get routed to the right implementation guide.