What problem does it solve? Developers integrating Clerk authentication face fragmented documentation across many frameworks and SDK versions, making it hard to find the correct pattern for their specific stack. ## Core Features & Use Cases - Task-Based Routing: Directs requests to the right sub-skill covering setup, CLI operations, custom UI, organizations, billing, webhooks, and testing. - Framework Coverage: Provides patterns for Next.js, React, Vue, Nuxt, Astro, TanStack Start, Expo, React Router, Chrome Extensions, Swift, and Android. - SDK Version Detection: Checks package.json to distinguish Core 2 from current SDK packages and applies the matching API patterns. - Use Case: A developer building a multi-tenant Next.js SaaS asks how to add organization-based billing, and the router directs them to clerk-orgs and clerk-billing with the correct v7 SDK patterns. ## Quick Start Ask how to add Clerk authentication to your Next.js app and get routed to the correct setup and pattern guidance.