What problem does it solve? Developers integrating Clerk authentication face fragmented documentation across many frameworks and SDK versions, making it hard to find the right pattern for their specific stack. ## Core Features & Use Cases - Task-Based Routing: Directs requests to 19 specialized skills covering setup, CLI operations, custom UI, billing, organizations, webhooks, and testing. - Framework Coverage: Provides dedicated guidance for Next.js, React, Vue, Nuxt, Astro, TanStack Start, React Router, Expo, Chrome Extensions, Swift, and Android. - SDK Version Detection: Reads package.json to distinguish Core 2 from current SDK packages and applies the correct API patterns. - Use Case: A developer building a Next.js SaaS app asks how to add subscription billing; the router detects @clerk/nextjs v7 and routes to clerk-billing for PricingTable and plan gating patterns. ## Quick Start Ask how to add Clerk authentication to your project and describe your framework and task.