What problem does it solve?
It helps you avoid being boxed in by Clerk’s default UI when you need a branded, fully custom authentication experience.
Core Features & Use Cases
- Custom authentication flows: Build your own sign-in and sign-up screens with the appropriate hooks (Core 2: useSignIn/useSignUp; Current SDK: useSignIn with namespaced methods).
- Appearance customization: Style Clerk components using the appearance prop (themes, variables like colors and border radius, layout/options including logos and social button variants, and bring-your-own CSS).
- Conditional UI rendering support: Use the correct component pattern for the SDK version (including the Core 3 Show pattern).
Use case: You’re launching a client-facing app that must match your design system and handle MFA, email/phone codes, and redirects with a custom sign-in form while ensuring Clerk’s prebuilt components follow your branding.
Quick Start
Customize your Clerk sign-in by selecting the correct core version, then apply an appearance object (variables and options) to your SignIn/SignUp components and wire the matching hook-based flow for your auth steps.