clerk

Route Clerk authentication tasks to framework-specific integration patterns.

1|3|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/kunmath/split-it --skill clerk-kunmath
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clerk
Source: https://github.com/kunmath/split-it/tree/main/.agents/skills/clerk
Command: npx skills add https://github.com/kunmath/split-it --skill clerk-kunmath

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically routes user requests to the appropriate Clerk authentication patterns, simplifying integration of Clerk across frameworks and platforms (Next.js, React, Vue, Nuxt, Expo, Astro, Chrome extensions, and mobile sign-in flows).

Core Features & Use Cases

  • Flexible routing to Clerk authentication flows based on the task, supporting sign-in, sign-up, and user management.
  • Framework-aware guidance that adapts to the detected Clerk SDK version (Core 2 vs Current) and platform specifics.
  • Wide applicability across web and mobile patterns, including Next.js, React, Vue, Nuxt, Expo, Astro, TanStack Start, and Chrome Extensions.

Quick Start

Configure the skill to automatically route Clerk auth tasks to the correct implementation for your project.

Frequently Asked Questions about clerk

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

FAQPage Schema
How do I implement Clerk authentication across different web frameworks?

Clerk authentication routing selects the correct pattern based on detected project dependencies and frontmatter metadata. It supports Next.js, React, Vue, Nuxt, and Astro by providing framework-aware guidance for sign-in, sign-up, and user-management flows.

Does Clerk auth work with Expo and Chrome extensions?

Yes, Clerk auth supports multi-platform flows including Expo and Chrome extensions. It routes authentication tasks to the correct integration flow by verifying environment requirements and adapting to platform specifics for mobile and extension sign-in patterns.

What is the best way to manage Clerk SDK version differences?

Managing Clerk SDK versions requires framework-aware guidance that adapts to the detected Clerk SDK version. The routing mechanism selects appropriate templates by checking version-aware requirements, ensuring compatibility between Core 2 and Current SDK versions.

How do I route sign-up and user-management tasks in Clerk?

Routing sign-up and user-management tasks in Clerk involves matching the user request to the appropriate authentication pattern. The skill uses frontmatter metadata and project dependencies to select templates and verify environment requirements for the specific flow.

Can I use Clerk authentication patterns with TanStack Start?

Yes, Clerk authentication patterns support TanStack Start alongside other frameworks. The routing mechanism detects the framework through project dependencies and frontmatter to ensure the correct integration flow is applied for the environment.