forge-frontend-nextjs

What problem does it solve?

It prevents AI-generated Next.js code from falling back to client components, client-side fetching, legacy routing patterns, and incorrect caching/streaming behavior—so your app router projects stay server-first, type-correct, and performant.

Core Features & Use Cases

• Server-first React Server Components: Enforces that layouts/pages default to server, with client boundaries pushed as deep as possible.
• Correct app-router data fetching & caching: Moves initial data loading out of useEffect into async server components and requires Next fetch cache controls for stability.
• Streaming, Suspense, and segment conventions: Requires Suspense for slow UI and uses loading.tsx, error.tsx, and not-found handling per segment.
• Server actions for mutations: Replaces trivial mutation API routes with server actions and promotes safe return shapes for failures.
• Next 16+ routing correctness: Ensures async params/searchParams are awaited to avoid type errors and runtime issues.

Quick Start

Use forge-frontend-nextjs when you need an AI to write a Next.js 16 app-router page that uses React Server Components, Suspense, loading/error segments, correct async params handling, and server actions instead of client-side useEffect fetching.