What problem does it solve?
Prevents hydration mismatches, SSR/client rendering differences, and route-level caching or rendering errors that break user experience and SEO in Nuxt 4 applications.
Core Features & Use Cases
- Hydration Safety Guidance: Keep the first render deterministic, move browser-only logic to mounted hooks or client-only components, and avoid client-only values in SSR-rendered markup.
- Data Fetching Patterns: Recommend when to use useFetch versus useAsyncData, how to give stable keys, when to use lazy fetching or server:false, and strategies to trim payload size.
- Route and Performance Strategies: Advise routeRules for prerender, SWR, ISR, and client-only pages, and provide lazy loading and lazy hydration techniques for large interactive islands.
- Review Checklist: Validate first SSR vs hydrated markup parity, ensure page data is hydrated from server-safe fetches, verify non-critical data is lazy with loading UI, and match routeRules to SEO and freshness requirements.
Quick Start
Use the nuxt4-patterns skill to diagnose hydration mismatches and recommend concrete fixes for a Nuxt 4 page that uses useFetch and dynamic route parameters.