clerk-custom-ui

tarafından clerk

We need to translate the given English text into Turkish, preserving the name "clerk-custom-ui" if it appears. The text is about building custom authentication flows and branding Clerk components. The name "clerk-custom-ui" does not appear in the provided text, so we don't include it. We must not add any extra commentary, labels, or formatting. Just the translation. The text: "Build custom authentication flows and visually brand Clerk components with hooks and appearance styling. Provides useSignIn and useSignUp hooks for building custom sign-in/sign-up UI; API differs between Core 2 and current SDK versions Appearance customization via variables (colors, typography, borders), options (logo, social button layout), and pre-built themes (dark, neobrutalism, shadcn, simple) shadcn theme automatically matches shadcn/ui projects when components.json is present; theme..." We need to translate accurately. Note: "Clerk" is a product name, keep as is. "useSignIn", "useSignUp", "Core 2

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

Custom UI

Prerequisite: Ensure ClerkProvider wraps your app. See clerk-setup skill.

Version: Check package.json for the SDK version — see clerk skill for the version table. This determines which custom flow references to use below.

This skill covers two areas:

  1. Custom authentication flows — build your own sign-in/sign-up UI with hooks
  2. Appearance customization — theme, style, and brand Clerk's pre-built components

What Do You Need?

TaskReference
Custom sign-in (Core 2 / LTS)core-2/custom-sign-in.md
Custom sign-up (Core 2 / LTS)core-2/custom-sign-up.md
Custom sign-in (Current SDK v7+)core-3/custom-sign-in.md
Custom sign-up (Current SDK v7+)core-3/custom-sign-up.md
Show component pattern (Current SDK)core-3/show-component.md

Custom Flow References

TaskCore 2Current
Custom sign-in (useSignIn)core-2/custom-sign-in.mdcore-3/custom-sign-in.md
Custom sign-up (useSignUp)core-2/custom-sign-up.mdcore-3/custom-sign-up.md
<Show> component(use <SignedIn>, <SignedOut>, <Protect>)core-3/show-component.md

Appearance Customization

Appearance customization applies to both Core 2 and the current SDK.

Component Customization Options

TaskDocumentation
Appearance prop overviewhttps://clerk.com/docs/nextjs/guides/customizing-clerk/appearance-prop/overview
Options (structure, logo, buttons)https://clerk.com/docs/nextjs/guides/customizing-clerk/appearance-prop/layout
Themes (pre-built dark/light)https://clerk.com/docs/nextjs/guides/customizing-clerk/appearance-prop/themes
Variables (colors, fonts, spacing)https://clerk.com/docs/nextjs/guides/customizing-clerk/appearance-prop/variables
CAPTCHA configurationhttps://clerk.com/docs/nextjs/guides/customizing-clerk/appearance-prop/captcha
Bring your own CSShttps://clerk.com/docs/nextjs/guides/customizing-clerk/appearance-prop/bring-your-own-css

Appearance Pattern

<SignIn
  appearance={{
    variables: {
      colorPrimary: '#0000ff',
      borderRadius: '0.5rem',
    },
    options: {
      logoImageUrl: '/logo.png',
      socialButtonsVariant: 'iconButton',
    },
  }}
/>

Core 2 ONLY (skip if current SDK): The options property was named layout. Use layout: { logoImageUrl: '...', socialButtonsVariant: '...' } instead of options.

variables (colors, typography, borders)

PropertyDescription
colorPrimaryPrimary color throughout
colorBackgroundBackground color
borderRadiusBorder radius (default: 0.375rem)

Opacity change: colorRing and colorModalBackdrop now render at full opacity. Use explicit rgba() values if you need transparency.

Core 2 ONLY (skip if current SDK): colorRing and colorModalBackdrop rendered at 15% opacity by default.

options (structure, logo, social buttons)

PropertyDescription
logoImageUrlURL to custom logo
socialButtonsVariant'blockButton' | 'iconButton' | 'auto'
socialButtonsPlacement'top' | 'bottom'
showOptionalFieldsShow optional fields (default: false)

Core 2 ONLY (skip if current SDK): This property is called layout, not options. Also, showOptionalFields defaulted to true.

Themes

Install themes from @clerk/ui:

npm install @clerk/ui
import { dark } from '@clerk/ui/themes'

<ClerkProvider appearance={{ theme: dark }} />

Core 2 ONLY (skip if current SDK): Themes are imported from @clerk/themes (install @clerk/themes instead of @clerk/ui). Example: import { dark } from '@clerk/themes'.

Theme stacking — pass an array where the last theme takes precedence:

import { dark, neobrutalism } from '@clerk/ui/themes'

<ClerkProvider appearance={{ theme: [dark, neobrutalism] }} />

CSS color-scheme support — the default theme respects the CSS color-scheme property for automatic light/dark mode toggling.

Available themes: dark, neobrutalism, shadcn, simple

shadcn Theme

IMPORTANT: If the project has components.json (shadcn/ui installed), ALWAYS apply the shadcn theme as the FIRST customization step. This ensures Clerk components visually match the existing shadcn design system. Skip this only if the user explicitly requests a different theme.

If the project uses shadcn/ui (check for components.json in the project root), always use the shadcn theme:

import { shadcn } from '@clerk/ui/themes'

<ClerkProvider appearance={{ theme: shadcn }} />

Also import shadcn CSS in your global styles:

@import 'tailwindcss';
@import '@clerk/ui/themes/shadcn.css';

Core 2 ONLY (skip if current SDK): Import from @clerk/themes and @clerk/themes/shadcn.css:

import { shadcn } from '@clerk/themes'
@import '@clerk/themes/shadcn.css';

Workflow

  1. Identify customization needs (custom flow or appearance)
  2. For custom flows: check SDK version → read appropriate core-2/ or core-3/ reference
  3. For appearance: WebFetch the appropriate documentation from table above
  4. Apply appearance prop to your Clerk components or build custom flow with hooks

Common Pitfalls

IssueSolution
Colors not applyingUse colorPrimary not primaryColor
Logo not showingPut logoImageUrl inside options: {} (or layout: {} in Core 2)
Social buttons wrongAdd socialButtonsVariant: 'iconButton' in options (or layout in Core 2)
Styling not workingUse appearance prop, not direct CSS (unless with bring-your-own-css)
Hook returns different shapeCheck SDK version — Core 2 and current have completely different useSignIn/useSignUp APIs

See Also

  • clerk-setup - Initial Clerk install
  • clerk-nextjs-patterns - Next.js patterns
  • clerk-orgs - B2B organizations

clerk tarafından daha fazla skill

clerk-monorepo
clerk
clerk/javascript SDK monorepo'sunda etkili bir şekilde çalışın. Depoyu kurarken, bir paketi derlerken/test ederken/çalıştırırken, @clerk/*… paketlerinden hangisini kullanacağınıza karar verirken kullanın.
official
mosaic
clerk
Work on Mosaic UI: styling a component with slot recipes (`defineSlotRecipe` / `useRecipe` / slots / variants), or building a flow — authoring a state machine…
official
mosaic-machine
clerk
Mosaic durum makinelerini yazın ve kullanın. Kullanıcının createMachine ile bir durum makinesi yazdığı, çok adımlı bir akış modellediği, bir makineyi React'e bağladığı durumlarda kullanın.
official
clerk-android
clerk
Implement Clerk authentication for native Android apps using Kotlin and Jetpack Compose with clerk-android source-guided patterns. Use for prebuilt…
official
clerk-astro-patterns
clerk
Clerk ile Astro desenleri — middleware, SSR sayfaları, island bileşenleri, API route'ları, statik ve SSR render etme. Tetikleyiciler: astro clerk, clerk astro middleware,…
official
clerk-backend-api
clerk
Clerk Backend REST API gezgini ve yürütücüsü. Etiketlere göz atın, uç nokta şemalarını inceleyin ve kimliği doğrulanmış istekler yürütün. Kullanıcıları listelerken, yönetirken… kullanın.
official
clerk-chrome-extension-patterns
clerk
Chrome Eklentisi kimlik doğrulaması @clerk/chrome-extension ile -- popup/sidepanel kurulumu, web uygulaması üzerinden OAuth/SAML için syncHost, service worker'lar ve… için createClerkClient
official
clerk-cli
clerk
Operate the Clerk CLI (`clerk` binary) for authentication, user/org/session management, impersonation, local webhook testing, deploy verification, instance…
official