clerk by clerk/skills
npx skills add https://github.com/clerk/skills --skill clerk检查 package.json 以确定 Clerk SDK 版本。这将决定使用哪种模式:
| 包 | Core 2 (LTS 支持至 2027 年 1 月) | 当前版本 |
|---|---|---|
@clerk/nextjs | v5–v6 | v7+ |
@clerk/react 或 @clerk/clerk-react | v5–v6 | v7+ |
@clerk/expo 或 @clerk/clerk-expo |
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
| v1–v2 |
| v3+ |
@clerk/react-router | v1–v2 | v3+ |
@clerk/tanstack-react-start | < v0.26.0 | v0.26.0+ |
如果版本不明确或项目是新的,默认使用当前版本。Core 2 包使用 @clerk/clerk-react 和 @clerk/clerk-expo(带有 clerk- 前缀);当前版本包使用 @clerk/react 和 @clerk/expo。
所有技能都是为当前 SDK 编写的。当 Core 2 中存在差异时,会在行内用 > **Core 2 ONLY (skip if current SDK):** 标注说明。例外情况是 clerk-custom-ui,它针对自定义流程钩子有单独的 core-2/ 和 core-3/ 目录,因为这些 API 在不同版本间完全不同。
将 Clerk 添加到你的项目 → 使用 clerk-setup
自定义登录/注册界面 → 使用 clerk-custom-ui
useSignIn / useSignUp 钩子的自定义身份验证流程<Show> 组件高级 Next.js 模式 → 使用 clerk-nextjs-patterns
B2B / 组织 → 使用 clerk-orgs
Webhooks → 使用 clerk-webhooks
端到端测试 → 使用 clerk-testing
Swift / 原生 iOS 身份验证 → 使用 clerk-swift
clerk-ios 的源代码驱动模式后端 REST API → 使用 clerk-backend-api
如果你知道你的任务,可以直接访问:
/clerk-setup - 框架设置/clerk-custom-ui - 自定义流程与外观/clerk-nextjs-patterns - Next.js 模式/clerk-orgs - 组织/clerk-webhooks - Webhooks/clerk-testing - 测试/clerk-swift - Swift/原生 iOS/clerk-backend-api - 后端 REST API或者描述你的需求,我会推荐合适的技能。
每周安装量
2.3K
代码仓库
GitHub 星标
22
首次出现
2026 年 1 月 26 日
安全审计
安装于
codex2.1K
opencode2.1K
gemini-cli2.0K
github-copilot2.0K
amp1.9K
kimi-cli1.9K
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-iosBackend 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-backend-api - Backend REST APIOr describe what you need and I'll recommend the right one.
Weekly Installs
2.3K
Repository
GitHub Stars
22
First Seen
Jan 26, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
codex2.1K
opencode2.1K
gemini-cli2.0K
github-copilot2.0K
amp1.9K
kimi-cli1.9K
99,500 周安装