npx claudepluginhub clerk/skills --plugin mobileThis skill uses the workspace's default tool permissions.
Check `package.json` to determine the Clerk SDK version. This determines which patterns to use:
Sets up Clerk authentication by detecting framework from package.json, fetching official quickstart docs via WebFetch, and applying instructions for Next.js, React, Vue, Astro, and more.
Installs Clerk SDK and configures authentication for Next.js, React, or Express apps. Sets up env vars, ClerkProvider, middleware, and verifies initial auth.
Provides expert Clerk auth patterns for Next.js App Router: ClerkProvider setup, SignIn/SignUp components, middleware route protection, and anti-patterns.
Share bugs, ideas, or general feedback.
Check package.json to determine the Clerk SDK version. This determines which patterns to use:
| Package | Core 2 (LTS until Jan 2027) | Current |
|---|---|---|
@clerk/nextjs | v5–v6 | v7+ |
@clerk/react or @clerk/clerk-react | v5–v6 | v7+ |
@clerk/expo or @clerk/clerk-expo | v1–v2 | v3+ |
@clerk/react-router | v1–v2 | v3+ |
@clerk/tanstack-react-start | < v0.26.0 | v0.26.0+ |
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
useSignIn / useSignUp hooks<Show> component for conditional renderingAdvanced Next.js patterns → Use clerk-nextjs-patterns
React patterns → Use clerk-react-patterns
useAuth, useUser, useClerk)React Router patterns → Use clerk-react-router-patterns
Vue patterns → Use clerk-vue-patterns
useAuth, useUser, useClerk)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
<PricingTable /> componenthas()Webhooks → Use clerk-webhooks
E2E Testing → Use clerk-testing
Swift / native iOS auth → Use clerk-swift
clerk-iosAndroid / native mobile auth → Use clerk-android
clerk-android-api and clerk-android-ui implementation guidanceclerk-androidBackend REST API → Use clerk-backend-api
If you know your task, you can directly access:
/clerk-setup - Framework setup/clerk-custom-ui - Custom flows & appearance/clerk-nextjs-patterns - Next.js patterns/clerk-react-patterns - React patterns/clerk-react-router-patterns - React Router patterns/clerk-vue-patterns - Vue patterns/clerk-nuxt-patterns - Nuxt patterns/clerk-astro-patterns - Astro patterns/clerk-tanstack-patterns - TanStack Start patterns/clerk-expo-patterns - Expo patterns/clerk-chrome-extension-patterns - Chrome Extension patterns/clerk-orgs - Organizations/clerk-billing - Billing & subscriptions/clerk-webhooks - Webhooks/clerk-testing - Testing/clerk-swift - Swift/native iOS/clerk-android - Native Android/clerk-backend-api - Backend REST APIOr describe what you need and I'll recommend the right one.