What problem does it solve?
Nuxt 4 apps often suffer from hydration mismatches, inefficient route-level rendering, oversized payloads, and incorrect data-fetching patterns that cause double requests or inconsistent client/server markup. This Skill provides practical patterns to make the first SSR render deterministic, select appropriate route rendering strategies, and safely migrate browser-only logic to the client.
Core Features & Use Cases
- Hydration Safety: Guidance to eliminate non-deterministic values on the server and move browser-only logic behind onMounted, import.meta.client, ClientOnly, or .client.vue components.
- Data Fetching Patterns: Recommendations for when to use useFetch, useAsyncData, stable keys, lazy fetching, and server:false to balance SEO and runtime performance.
- Route Rules & Caching: How to use routeRules for prerender, swr, isr, ssr:false, and Nitro cache controls to match SEO, freshness, and latency requirements.
- Performance & Lazy Hydration: Tactics for code-splitting, lazy components, and lazy hydration strategies for heavy interactive islands.
- Use Case Example: Diagnose a blog article page that shows hydration mismatches and large payloads; move comment fetching to lazy useFetch with server:false and give useAsyncData a stable key for the article body.
Quick Start
Analyze a Nuxt 4 page with a hydration mismatch and produce a prioritized remediation plan covering useFetch/useAsyncData adjustments, routeRules changes, and lazy-hydration or client-only segregation.