What problem does it solve? Nuxt 4 apps often suffer from hydration mismatches, inefficient data fetching, and poorly chosen rendering strategies. This Skill provides concrete patterns to diagnose and fix these issues when building or debugging SSR and hybrid-rendered Nuxt applications. ## Core Features & Use Cases - Hydration Safety: Guidance for keeping server-rendered markup deterministic, isolating browser-only logic with onMounted, import.meta.client, ClientOnly, and .client.vue components. - SSR-Safe Data Fetching: Rules for choosing between useFetch, useAsyncData, $fetch, and lazy variants, including payload trimming with pick and stable cache keys. - Route Rules & Performance: Configuration patterns for prerender, SWR, ISR, and client-only routes in nuxt.config.ts, plus lazy component loading and lazy hydration strategies. - Use Case: When a Nuxt page shows hydration mismatch warnings after adding a timestamp or reading localStorage in a template, use this Skill to restructure the code so server and client renders match. ## Quick Start Ask the assistant to review your Nuxt 4 page or component for hydration safety and correct useFetch or useAsyncData usage.