What problem does it solve?
The Clerk router removes uncertainty about which Clerk pattern or setup to use by interpreting developer needs and directing them to the specific skill that handles framework setup, custom UI, mobile auth, backend API usage, testing, organizations, or webhooks.
Core Features & Use Cases
- Central routing: Maps user requests to focused Clerk skills such as clerk-setup, clerk-custom-ui, clerk-nextjs-patterns, or clerk-swift.
- SDK version detection: Inspects package.json to choose Core 2 vs current SDK patterns and notes Core 2 differences where needed.
- Use Case: When a developer asks how to add authentication in a Next.js app, the router detects the SDK version and routes to clerk-nextjs-patterns with the appropriate middleware and server/client guidance.
Quick Start
Ask the clerk skill to route you by describing your project framework, the Clerk SDK version if known, and the authentication outcome you need so it can recommend the exact sub-skill and next steps.