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 via definePageMeta or create custom route middleware with useAuth for redirect logic. - Server API Auth: Access event.context.auth in Nitro server routes and use clerkClient from @clerk/nuxt/server to fetch user data with proper 401/403 handling. - Composables & SSR: Use auto-imported useAuth, useUser, and useClerk composables with SSR-safe patterns that avoid hydration mismatches. - Use Case: You are building a Nuxt SaaS dashboard and need to protect /dashboard, return the current user from a Nitro API route, and add organization switching. This Skill gives you the exact middleware, server route, and OrganizationSwitcher patterns to implement all three. ## Quick Start Ask the AI to protect the /dashboard route in your Nuxt 3 app with Clerk authentication and redirect unauthenticated users to the sign-in page.