What problem does it solve?
This Skill helps developers identify and fix Nuxt 4 SSR and hydration mismatches, routing rendering decisions, and inefficient data-fetch patterns that cause broken UI, duplicate requests, or oversized payloads.
Core Features & Use Cases
- Hydration safety guidance: Identify server-only vs client-only logic and show where to move browser-only APIs to onMounted, ClientOnly, or .client.vue boundaries.
- SSR-safe data fetching: Recommend when to use useFetch, useAsyncData, lazy fetches, or server: false and how to provide stable keys and avoid side effects.
- Route rendering strategies: Advise routeRules for prerender, swr, isr, ssr:false and Nitro cache behaviors to match SEO and freshness needs.
- Performance patterns: Suggest lazy-loading, delayed hydration, payload trimming with pick, and component splitting to reduce initial payload and improve TTI.
- Use Case: Debug a blog with hydration mismatches and update data fetching to use useAsyncData with stable keys while applying routeRules for ISR.
Quick Start
Use the nuxt4-patterns guidance to diagnose hydration mismatches, convert unsafe SSR code to client-only hooks, and recommend routeRules and lazy loading strategies.