What problem does it solve? Developers working with 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 specialized skills covering setup, CLI operations, custom UI, organizations, billing, webhooks, and testing. - Framework Coverage: Provides patterns for Next.js, React, Vue, Nuxt, Astro, TanStack Start, React Router, Expo, Chrome Extensions, Swift, and Android. - SDK Version Detection: Checks package.json to distinguish Core 2 from current Clerk SDK versions and applies the correct patterns. - Use Case: A developer building a multi-tenant Next.js SaaS asks about organization slugs and seat-based billing, and gets routed to the clerk-orgs and clerk-billing skills with version-appropriate code. ## Quick Start Ask how to add Clerk authentication with organizations and billing to your Next.js app.