clerk-custom-ui

Create custom Clerk authentication UI with useSignIn and useSignUp hooks.

Updated Aug 27, 2026

Search Tags:#authentication #themes #shadcn #clerk #sign-in #custom ui #appearance prop

Ready to run

npx skills add https://github.com/MichaelFrieze/riffatlas --skill clerk-custom-ui-michaelfrieze

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clerk-custom-ui
Source: https://github.com/MichaelFrieze/riffatlas/tree/main/.agents/skills/clerk-custom-ui
Command: npx skills add https://github.com/MichaelFrieze/riffatlas --skill clerk-custom-ui-michaelfrieze

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you build custom Clerk authentication experiences while keeping the UI consistent with your app’s design system, including both custom sign-in/sign-up flows and full appearance theming.

Core Features & Use Cases

Custom authentication flows with hooks: Implement your own sign-in and sign-up user interface using the appropriate useSignIn and useSignUp APIs for the Clerk SDK version.
Appearance customization for Clerk components: Control theme, colors, typography, borders, CAPTCHA behavior, and structure/branding through the appearance prop.
SDK-aware implementation guidance: Choose the correct reference docs based on whether you’re using Core 2 or the current SDK, avoiding API mismatches.

Quick Start

Use the clerk-custom-ui skill to design your custom sign-in and appearance customization by selecting the correct Core 2 or current SDK hook references, then apply the appearance prop to Clerk’s sign-in/sign-up components.

Frequently Asked Questions about clerk-custom-ui

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I customize Clerk sign-in and sign-up UI components?▼

To build custom Clerk sign-in flows, use the useSignIn and useSignUp hooks to implement your own UI components. This approach allows you to create branded authentication experiences while maintaining full control over the user interface layout and design.

Can I use shadcn themes with Clerk authentication components?▼

Yes, Clerk's appearance prop supports optional shadcn integration for styling authentication components. You can apply shadcn themes and variables through the appearance configuration to ensure your Clerk sign-in and sign-up flows match your shadcn-based design system.

What's the best way to create a branded Clerk sign-in experience?▼

The best way to create a branded Clerk sign-in experience is by combining the appearance prop for component theming with custom flows built using useSignIn and useSignUp hooks. Configure ClerkProvider appearance to control themes, variables, and layout options for consistent branding.

Do I need different Clerk hooks for Core 2 vs current SDK versions?▼

Yes, Clerk SDK versions require different hook references. The skill provides SDK-aware documentation selection, helping you choose the correct Core 2 or current SDK references for useSignIn and useSignUp APIs to avoid version mismatches and ensure proper authentication flow implementation.

How does the Clerk appearance prop work for theming authentication components?▼

The Clerk appearance prop controls theme, colors, typography, borders, CAPTCHA behavior, and branding structure for authentication components. Set on the ClerkProvider, it drives theming for Clerk's built-in sign-in and sign-up components as well as custom flow rendering.

Why are my custom Clerk authentication hooks not working correctly?▼

Custom Clerk hooks may not work correctly if you are using the wrong SDK version references. The useSignIn and useSignUp APIs differ between Core 2 and the current SDK. Selecting the wrong reference docs can cause API mismatches and break your authentication flows.