clerk-nextjs-patterns

Clerk authentication in Next.js server and client components is implemented by applying specific auth APIs for server-side logic and client hooks for hybrid workflows. This Skill provides patterns to correctly handle both environments and avoid common auth mistakes.

Protecting routes and Server Actions with Clerk is achieved through middleware configurations and permission checks. This Skill provides patterns for securing API routes, Server Actions, and organization-based access control to ensure authorized access.

Custom JWTs and session verification are supported for Next.js API routes with Clerk. This Skill shows how to integrate custom JWTs, verify sessions, and implement safe user-scoped caching for production applications.

Clerk middleware does work for organization-based access control in Next.js by intercepting requests to verify permissions. This Skill provides patterns to secure middleware, API routes, and Server Actions based on organization roles.

Next.js server-side caching fails with Clerk user sessions when data is not properly scoped to the authenticated user. This Skill provides safe user-scoped caching patterns to ensure data isolation and prevent unauthorized access.

Converting a Next.js dashboard from client hooks to secure server-side Clerk auth involves migrating authentication logic to Server Components and middleware. This Skill provides the patterns to secure server actions, routes, and user-scoped data access.