clerk

To add Clerk authentication, you initialize the SDK, configure environment variables, and use framework-specific routing patterns to protect routes. This skill guides you through SDK setup and applies the correct protection approach for your app.

Yes, you can build a custom sign-in and sign-up UI using Clerk hooks and appearance patterns. This allows you to apply custom themes, layouts, and conditional rendering to match your application's design system.

Clerk authentication works across Next.js, React, Expo, Chrome Extensions, and other multi-framework applications. The skill automatically routes to the correct framework-specific setup and implementation patterns.

You set up Clerk organizations by implementing the B2B routing patterns provided by the SDK. This skill covers the production-ready scopes needed to manage organizations, handle billing, and process subscription webhooks.

You handle Clerk SDK version differences by detecting the installed version via package.json. This skill automatically applies the correct current-SDK patterns and provides Core 2 callouts when behavior differs.

The best way to run end-to-end testing for Clerk auth flows is to use the testing patterns covered by this skill. It supports setting up and executing E2E tests across web and native mobile platforms.