domains / families / software-engineering / clerk-auth

clerk-auth

combined

Clerk auth with API Keys beta (Dec 2025), Next.js 16 proxy.ts (March 2025 CVE context), API version 2025-11-10 breaking changes, clerkMiddleware() options, webhooks, production considerations (GCP outages), and component reference. Prevents 15 documented errors. Use when: API keys for users/orgs, Next.js 16 middleware filename, troubleshooting JWKS/CSRF/JWT/token-type-mismatch errors, webhook verification, user type inconsistencies, or testing with 424242 OTP. Expert patterns for Clerk auth implementation, middleware,

When to use

• User mentions or implies: adding authentication
• User mentions or implies: clerk auth
• User mentions or implies: user authentication
• User mentions or implies: sign in
• User mentions or implies: sign up
• User mentions or implies: user management
• User mentions or implies: multi-tenancy
• User mentions or implies: organizations

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The two copies cover different, non-overlapping material. The first is a generic wrapper that defers to an external detailed guide and lists trigger phrases. The second is a specific, versioned implementation guide covering Clerk API Keys beta, Next.js 16 proxy.ts middleware, API version 2025-11-10 breaking changes, and error prevention. Neither copy contains the other's core steps, so crowning one would hide a real alternative.