next-best-practices

Next.js best practices for server components and route handlers involve enforcing consistent file conventions, strict RSC boundaries, and standardized data-fetching patterns to ensure a scalable application architecture.

Audit a Next.js codebase by reviewing file structure, RSC boundaries, metadata usage, and error handling against established best practices to identify and resolve pattern violations for maintainability.

The best way to handle errors and metadata in a Next.js app is applying structured guidelines that standardize error boundaries and metadata generation across all route handlers and server components.

Yes, you can use Next.js best practices for scaffolding new projects and onboarding engineers by applying a standard structure and consistent patterns across file conventions, data fetching, and routing.

Yes, you need a root SKILL.md file with YAML frontmatter containing a name and description to provide the metadata fields required for applying these Next.js best practices and enabling automatic discovery.