What problem does it solve? Nuxt 4 applications 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 SSR or hybrid-rendered Nuxt apps. ## Core Features & Use Cases - Hydration Safety: Guidance for keeping the first render deterministic by moving browser-only logic behind onMounted, import.meta.client, ClientOnly, or .client.vue components. - SSR-Safe Data Fetching: Rules for choosing between useFetch, useAsyncData, $fetch, and lazy variants, including stable keys, payload trimming with pick, and pending-state handling. - 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 product page shows a hydration mismatch warning and loads slowly, apply this Skill to move browser-only code out of SSR markup, switch page data to useFetch, and add swr route rules for the catalog. ## Quick Start Review my Nuxt 4 page for hydration mismatches and rewrite its data fetching to use SSR-safe useFetch or useAsyncData patterns.