react-next-modern

Next.js App Router Server Components are enforced by shifting data fetching to the server and minimizing client-side effects. This skill applies during code reviews and migrations by generating steps to transition target modules away from client-heavy patterns toward server-driven architecture.

Server-first data fetching in React 19 and Next.js is enforced by shifting data retrieval to Server Components and Server Actions. This skill enforces these patterns during code reviews to reduce client-side fetching and reliance on useEffect.

Using useActionState and useFormStatus with Server Actions involves declarative form handling within a Next.js App Router workflow. This skill satisfies requirements for these React 19 form hooks by enforcing their use alongside Server Actions during code reviews.

Reviewing code for client-side effects in a Next.js App Router project involves identifying client-heavy patterns and useEffect reliance. This skill applies during code reviews to detect these patterns and generate migration steps toward modern React 19 Server Components.

Server Actions should be used instead of API routes when building declarative forms and server-driven data flows in a Next.js App Router workflow. This skill enforces Server Actions alongside hooks like useActionState to minimize client-side effects.