Next.js App Router Patterns

/plugin marketplace add wshobson/agents; /plugin install frontend-mobile-development

The default is a server component and 'use client' is spent deliberately, because every boundary crossed adds bundle weight and forces data to be serialisable. Rendering modes are laid out side by side — static, dynamic, streaming — with the revalidation and caching behaviour that decides which one a route actually gets. Parallel routes, intercepting routes and the file conventions around loading, error and not-found states are covered, along with Server Actions for mutations that still work before hydration.