What problem does it solve? Developers using Clerk for authentication often need to replace the default hosted UI with custom sign-in/sign-up flows or restyle Clerk components to match their brand, but the APIs differ significantly between SDK versions (Core 2 vs current SDK), causing confusion and broken implementations. ## Core Features & Use Cases - Custom Authentication Flows: Build bespoke sign-in and sign-up experiences using the useSignIn and useSignUp hooks, covering password, SSO/OAuth, passkey, Web3, email/phone OTP, MFA, password reset, and device trust. - Appearance Customization: Theme and style Clerk's pre-built components via the appearance prop — variables (colors, fonts, radius), options (logo, social buttons), and pre-built themes like dark, neobrutalism, and shadcn. - Version-Aware Guidance: Separate reference docs for Core 2 (older SDK) and the current SDK, so the correct hook API is used based on the project's installed version. - Use Case: A React app with shadcn/ui needs a branded login page with email OTP and MFA. The skill detects the SDK version, applies the shadcn theme to Clerk components, and provides the correct useSignIn custom flow code. ## Quick Start Ask the AI to build a custom Clerk sign-in page with email and password using the installed SDK version, applying the shadcn theme to match the app's design system.