clerk

Intelligent router that directs authentication tasks to specialized Clerk skills based on your framework and use case. Check package.json to determine the Clerk SDK version. This determines which patterns to use: Default to current if the version is unclear or the project is new. Core 2 packages use @clerk/clerk-react and @clerk/clerk-expo (with clerk- prefix); current packages use @clerk/react and @clerk/expo . All skills are written for the current SDK. When something differs in Core 2, it's noted inline with > **Core 2 ONLY (skip if current SDK):** callouts. The exception is clerk-custom-ui , which has separate core-2/ and core-3/ directories for custom flow hooks since those APIs are entirely different between versions. Adding Clerk to your project → Use clerk-setup Custom sign-in/sign-up UI → Use clerk-custom-ui Advanced Next.js patterns → Use clerk-nextjs-patterns React patterns → Use clerk-react-patterns React Router patterns → Use clerk-react-router-patterns Vue patterns → Use clerk-vue-patterns Nuxt patterns → Use clerk-nuxt-patterns Astro patterns → Use clerk-astro-patterns TanStack Start patterns → Use clerk-tanstack-patterns Expo patterns → Use clerk-expo-patterns Chrome Extension patterns → Use clerk-chrome-extension-patterns B2B / Organizations → Use clerk-orgs Billing & Subscriptions → Use clerk-billing Webhooks → Use clerk-webhooks E2E Testing → Use...