What problem does it solve? Adding authentication to a Nuxt 3 application involves many moving parts: route protection, server API auth, SSR hydration, and organization support. This Skill provides proven patterns for integrating @clerk/nuxt so you avoid common pitfalls like hydration mismatches, undefined composables on the server, and unprotected routes. ## Core Features & Use Cases - Route Protection: Use the built-in auth middleware with definePageMeta or create custom route middleware for org-scoped access control. - Server API Auth: Access event.context.auth and clerkClient in Nitro server routes to return 401/403 responses and fetch user data securely. - Composables & SSR: Use auto-imported useAuth, useUser, and useClerk composables with SSR-safe patterns that prevent hydration mismatches. - Use Case: You are building a Nuxt SaaS dashboard and need to protect /dashboard, expose an authenticated /api/user-data endpoint, and add organization switching in the header. This Skill gives you the exact middleware, server route, and component patterns to implement all three. ## Quick Start Ask the AI to protect the /dashboard route in your Nuxt 3 app with Clerk so unauthenticated users are redirected to the sign-in page.
