auth-components
Pre-built and custom Clerk authentication component templates with theming and customization patterns. Use when building authentication UI, creating sign-in/sign-up pages, customizing Clerk components, implementing user buttons, theming auth flows, or when user mentions Clerk components, SignIn, SignUp, UserButton, auth UI, appearance customization, or authentication theming.
What this skill does
# Clerk Auth Components Skill
This skill provides comprehensive templates and patterns for implementing and customizing Clerk authentication components including pre-built components, Clerk Elements for custom flows, and appearance theming.
## Overview
Clerk offers two approaches for authentication UI:
1. **Pre-built Components** - Ready-to-use `<SignIn />`, `<SignUp />`, `<UserButton />` with minimal configuration
2. **Clerk Elements** - Custom components with granular control for advanced use-cases
This skill covers both approaches with practical templates and customization patterns.
## Available Scripts
### 1. Generate Authentication UI Pages
**Script**: `scripts/generate-auth-ui.sh <output-dir> <component-type>`
**Purpose**: Generates complete authentication page templates
**Component Types**:
- `signin` - SignIn page with routing
- `signup` - SignUp page with routing
- `both` - Both SignIn and SignUp pages
- `profile` - User profile page
- `all` - Complete auth UI set
**Usage**:
```bash
# Generate sign-in page
./scripts/generate-auth-ui.sh ./app/sign-in signin
# Generate both sign-in and sign-up
./scripts/generate-auth-ui.sh ./app signup
# Generate complete auth UI
./scripts/generate-auth-ui.sh ./app all
```
**Generated Files**:
- `app/sign-in/[[...sign-in]]/page.tsx`
- `app/sign-up/[[...sign-up]]/page.tsx`
- `app/profile/[[...profile]]/page.tsx`
- `components/auth/protected-wrapper.tsx`
### 2. Customize Appearance and Theming
**Script**: `scripts/customize-appearance.sh <config-file> <theme-preset>`
**Purpose**: Generates appearance configuration for Clerk components
**Theme Presets**:
- `default` - Clerk default theme
- `dark` - Dark mode theme
- `neobrutalist` - Neobrutalist theme
- `shadesOfPurple` - Shades of Purple theme
- `custom` - Custom theme template
**Usage**:
```bash
# Generate dark theme config
./scripts/customize-appearance.sh ./lib/clerk-config.ts dark
# Generate custom theme template
./scripts/customize-appearance.sh ./lib/clerk-config.ts custom
# Generate theme with custom variables
BRAND_COLOR="#6366f1" ./scripts/customize-appearance.sh ./lib/clerk-config.ts custom
```
**Environment Variables**:
- `BRAND_COLOR` - Primary brand color (hex)
- `BACKGROUND` - Background color (hex)
- `TEXT_COLOR` - Text color (hex)
### 3. Validate Component Implementation
**Script**: `scripts/validate-components.sh <project-dir>`
**Purpose**: Validates Clerk component setup and configuration
**Checks**:
- Clerk dependencies installed (@clerk/nextjs)
- Environment variables configured
- ClerkProvider setup in layout
- Authentication pages exist
- Middleware configured
- No hardcoded secrets
**Usage**:
```bash
# Validate current project
./scripts/validate-components.sh .
# Validate specific directory
./scripts/validate-components.sh /path/to/project
```
**Exit Codes**:
- `0`: Validation passed
- `1`: Validation failed (must fix issues)
## Available Templates
### 1. Sign-In Page Template
**Template**: `templates/sign-in-page.tsx`
**Features**:
- Next.js App Router integration
- Catch-all routing `[[...sign-in]]`
- After sign-in redirect configuration
- Centered layout with responsive design
**Usage**:
```typescript
// app/sign-in/[[...sign-in]]/page.tsx
import { SignIn } from '@clerk/nextjs'
export default function SignInPage() {
return (
<div className="flex min-h-screen items-center justify-center">
<SignIn
appearance={{
elements: {
rootBox: "mx-auto",
card: "shadow-lg"
}
}}
afterSignInUrl="/dashboard"
/>
</div>
)
}
```
### 2. Sign-Up Page Template
**Template**: `templates/sign-up-page.tsx`
**Features**:
- Next.js App Router integration
- Catch-all routing `[[...sign-up]]`
- After sign-up redirect configuration
- Custom appearance configuration
### 3. Custom User Button Template
**Template**: `templates/user-button-custom.tsx`
**Features**:
- Custom menu items
- Appearance customization
- Avatar size control
- Dropdown actions
**Customization Example**:
```typescript
<UserButton
appearance={{
elements: {
userButtonAvatarBox: "w-10 h-10",
userButtonPopoverCard: "shadow-xl"
}
}}
>
<UserButton.MenuItems>
<UserButton.Link
label="Dashboard"
labelIcon={<LayoutDashboard size={16} />}
href="/dashboard"
/>
<UserButton.Action
label="Settings"
labelIcon={<Settings size={16} />}
onClick={() => router.push('/settings')}
/>
</UserButton.MenuItems>
</UserButton>
```
### 4. Protected Route Wrapper
**Template**: `templates/protected-wrapper.tsx`
**Features**:
- Authentication guard for routes
- Loading states
- Redirect configuration
- Reusable HOC pattern
**Usage**:
```typescript
// app/dashboard/page.tsx
import { ProtectedRoute } from '@/components/auth/protected-wrapper'
export default function DashboardPage() {
return (
<ProtectedRoute>
<div>Protected Dashboard Content</div>
</ProtectedRoute>
)
}
```
## Available Examples
### 1. Custom Sign-In with Clerk Elements
**Example**: `examples/custom-sign-in-guide.md` (code: `examples/custom-sign-in.tsx`)
**Demonstrates**:
- Clerk Elements for custom sign-in flow
- Step-based authentication
- Strategy selection (password, OAuth)
- Form validation
- Error handling
- Custom styling
**Key Components**:
```typescript
<SignIn.Root>
<SignIn.Step name="start">
{/* Email/username input */}
<SignIn.Strategy name="password">
{/* Password input */}
</SignIn.Strategy>
<SignIn.Strategy name="email_code">
{/* Email verification */}
</SignIn.Strategy>
</SignIn.Step>
</SignIn.Root>
```
### 2. Social Authentication Buttons
**Example**: `examples/social-authentication-guide.md` (code: `examples/social-buttons.tsx`)
**Demonstrates**:
- OAuth provider buttons
- Custom social button styling
- Loading states
- Error handling
- Multiple providers (Google, GitHub, Discord)
**Supported Providers**:
- Google
- GitHub
- Discord
- Microsoft
- Facebook
- Apple
### 3. Complete Theme Configuration
**Example**: `examples/theming-guide.md` (code: `examples/theme-config.tsx`)
**Demonstrates**:
- Complete appearance configuration
- CSS variables customization
- Layout configuration
- Element-specific styling
- Dark mode support
- Responsive design
## Appearance Customization Guide
### 1. Appearance Prop Structure
The `appearance` prop accepts:
```typescript
appearance={{
baseTheme: dark, // Base theme
layout: { // Layout options
shimmer: true,
logoPlacement: 'inside'
},
variables: { // CSS variables
colorPrimary: '#6366f1',
colorBackground: '#ffffff',
colorText: '#1f2937',
borderRadius: '0.5rem'
},
elements: { // Element overrides
card: 'shadow-lg',
formButtonPrimary: 'bg-blue-500',
footerActionLink: 'text-blue-600'
}
}}
```
### 2. Global vs Component-Level Theming
**Global (ClerkProvider)**:
```typescript
<ClerkProvider appearance={{
baseTheme: dark,
variables: { colorPrimary: '#6366f1' }
}}>
{children}
</ClerkProvider>
```
**Component-Level**:
```typescript
<SignIn appearance={{
elements: {
card: 'shadow-xl',
rootBox: 'mx-auto'
}
}} />
```
### 3. Tailwind CSS v4 Integration
For Tailwind CSS v4 support:
```typescript
<ClerkProvider
appearance={{
cssLayerName: 'clerk' // Ensures Tailwind utilities override
}}
>
```
### 4. Element Targeting
Common element selectors:
- `rootBox` - Root container
- `card` - Main card container
- `headerTitle` - Header text
- `formButtonPrimary` - Submit buttons
- `formFieldInput` - Input fields
- `footerActionLink` - Footer links
- `userButtonAvatarBox` - User avatar
- `userButtonPopoverCard` - Dropdown menu
## Security Compliance
This skill follows strict security rules:
- All code examples use placeholder values only
- No real API keys, passwords, or secrets
- Environment variable references iRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.