clerk

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 B2B / Organizations → Use clerk-orgs Webhooks → Use clerk-webhooks E2E Testing → Use clerk-testing Swift / native iOS auth → Use clerk-swift Android / native mobile auth → Use clerk-android Backend REST API → Use clerk-backend-api If you know your task, you can directly access: Or describe what you need and I'll recommend the right one. - Framework detection and quickstart - Environment setup, API keys, Keyless flow - Migration from other auth providers - Custom authentication flows with useSignIn / useSignUp hooks - Appearance and styling (themes, colors, layout) - component for conditional rendering - Server vs Client auth...