next-best-practices

To check Next.js best practices, audit your project against file conventions, RSC boundaries, and data patterns. This skill provides a structured checklist to review route files, async APIs, and error boundaries, generating actionable remediation steps for any deviations.

Correct Next.js routing and metadata structure follows file conventions for app layouts and parallel routes. Use generateMetadata for dynamic metadata, maintain proper Server Component boundaries, and implement error boundaries to align with recommended Next.js patterns.

You audit Next.js bundling and error handling by applying a checklist that verifies error boundaries, route handlers, and bundling configurations. This generates a remediation plan to align your repository with optimization guidelines and robust data patterns.

Yes, you can use this Next.js best practices audit on an existing project. It evaluates your current codebase against guidelines for file conventions, RSC boundaries, and metadata usage, then provides a starter audit checklist and prompt templates to generate remediation steps.

The limitation of using a checklist for Next.js RSC boundaries is that it provides a basic structured audit rather than automated runtime enforcement. It guides manual reviews of Server vs Client Components and data fetching but requires developer intervention to implement the generated remediation steps.