What problem does it solve?
This Skill routes your Clerk authentication and integration request to the correct, framework- and task-specific guidance so you don’t have to hunt through unrelated docs or patterns.
Core Features & Use Cases
- Task-based skill routing: Send broad or specific requests (Next.js, React, Vue, Nuxt, Astro, Expo, routing libraries, etc.) to the matching Clerk sub-skill such as setup, custom UI, orgs, billing, webhooks, or testing.
- SDK version-aware guidance: Detect the Clerk SDK version from the project package.json and apply the appropriate patterns (current SDK vs Core 2 where relevant).
- Quick navigation by objective: Jump directly to topics like
/clerk-nextjs-patterns or /clerk-billing when you already know what you’re trying to implement.
Quick Start
Tell me what you’re building with Clerk (for example, “I’m adding Clerk auth to a Next.js app and I need to protect server actions and APIs—what should I do?”), and the router will select the appropriate sub-skill and next steps.