frontend-guidelines

To organize components in a Next.js App Router monorepo, colocate page-specific components inside a _components folder alongside the route's page.tsx, and centralize shared utilities under frontend/src/ to maintain a single source of truth.

Move a component to the shared frontend/src directory when it is reused across multiple routes, layouts, or features. Prefer colocated page-specific components first before promoting them to shared directories to maintain maintainable structure.

The best way to structure a multi-page Next.js application is to standardize frontend patterns by colocating route-specific components under _components and organizing shared code under frontend/src/ subdirectories like src/ui/ and src/shared/.

Yes, you need specific lint rules for frontend component placement to enforce the conventions of colocating page-specific components and maintaining a consistent naming structure across the Next.js App Router project.

This Next.js frontend architecture guideline targets multi-page app development using the App Router. While the shared frontend/src patterns might apply, the colocation conventions are specifically designed for multi-route and multi-page monorepo structures.