scaffold-page

Scaffolding a Next.js App Router page generates page.tsx, loading.tsx, and error.tsx files simultaneously. This establishes the expected server and client component split, providing immediate loading states and error boundaries for production-ready routes.

Structuring public and admin routes uses route group conventions to organize pages by access level. This approach places public, auth, customer, and admin pages into distinct directories, ensuring correct layout integration and metadata separation.

Adding Tailwind styling and metadata to a new Next.js page applies mobile-first design conventions automatically during scaffolding. This ensures the generated server components include proper route mapping and consistent styling fitted to the project.

Including database integration and zod validation when generating a Next.js page is supported as an optional configuration. This adds data fetching capabilities and form validation directly to the scaffolded server components for production use.

Manually configuring route groups for customer and auth pages is unnecessary. The scaffolding process automatically selects the correct placement based on FixNow conventions, applying the appropriate layout patterns and route mapping for each page type.