next-best-practices

Next.js best practices for routing and file structure codify standardized conventions for organizing modern applications, defining React Server Component boundaries, and structuring route handlers to ensure consistent project architecture across teams.

Handling errors and metadata in Next.js App Router projects requires following consolidated best-practice guidelines that define standardized rules for metadata generation and error-handling patterns to ensure application stability and correct SEO configuration.

This Next.js best practices guide serves as a reusable knowledge base for team onboarding and code reviews, providing standardized rules for data handling patterns and component boundaries to audit projects and extract actionable improvements.

The recommended way to structure React Server Components in Next.js involves applying standardized best-practice rules for RSC boundaries and data handling patterns, ensuring clear component separation and optimized performance in modern applications.

This Next.js best practices skill requires no external dependencies, functioning as a self-contained knowledge unit that defines file conventions and architecture guidelines through a SKILL.md frontmatter along with optional scripts and references directories.