next-best-practices

Enforce Next.js best practices by running a project review that checks RSC boundaries, file conventions, and routing against established patterns. This validates conformance and outputs actionable remediation steps to improve codebase maintainability and reliability.

The best way to handle errors and metadata is to validate your codebase against reference patterns for error handling and metadata strategies. This surfaces concrete remediation steps for any architectural deviations and ensures consistent, reliable application behavior.

Review a codebase for architecture drift by checking data patterns, runtime decisions, and RSC boundaries against reference documentation. This identifies deviations from Next.js best practices and outputs actionable recommendations to correct architectural inconsistencies.

Yes, you can apply this guidance during code reviews to validate route handlers and asset optimization. It establishes a shared playbook by identifying deviations from Next.js best practices and surfacing concrete remediation steps for the reviewed codebase.

No, this Next.js best practices review requires no external dependencies or libraries. It operates by reading the SKILL.md frontmatter and accompanying markdown references to validate conformance and provide actionable architecture recommendations.