菜单
Clerk authentication router. Use when user asks about adding authentication, setting up Clerk, custom sign-in flows, Swift or native iOS auth, native Android auth, Next.js patterns, organizations, syncing users, or testing. Automatically routes to the specific skill based on their task.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Clerk backend REST API
Custom authentication flows and component appearance - hooks (useSignIn, useSignUp), themes, colors, fonts, CSS. Use for custom sign-in/sign-up flows, appearance styling, visual customization, branding.
Advanced Next.js patterns - middleware, Server Actions, caching with Clerk.
Add Clerk authentication to any project by following the official quickstart guides.
E2E testing for Clerk apps. Use with Playwright or Cypress for auth flow tests.
Clerk webhooks for real-time events and data syncing. Listen for user creation, updates, deletion, and organization events. Build event-driven features like database sync, notifications, integrations.
| name | clerk |
| description | Clerk authentication router. Use when user asks about adding authentication, setting up Clerk, custom sign-in flows, Swift or native iOS auth, native Android auth, Next.js patterns, organizations, syncing users, or testing. Automatically routes to the specific skill based on their task. |
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
B2B / Organizations → Use clerk-orgs
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-orgs - Organizations/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.