next-best-practices

To fix RSC boundary violations in Next.js App Router, ensure server-to-client component props are fully serializable and avoid using async request APIs directly within Client Components. This Skill enforces those constraints during code review to prevent runtime boundary errors.

Next.js 15 async APIs like cookies() and params throw errors when not treated as Promises. This Skill applies the required Promise-based usage pattern for params, searchParams, cookies(), and headers(), including the generateMetadata flow, to resolve these issues.

The best way to handle error boundaries in Next.js is to implement error.tsx, global-error.tsx, and not-found.tsx file conventions. This Skill provides deterministic guidance on navigation and error-handling semantics to ensure reliable production behavior.

To prevent data waterfalls when choosing between Server Actions and Route Handlers, apply deterministic routing patterns that avoid conflicts. This Skill guides the correct mechanism selection between Server Components, Server Actions, and Route Handlers.

Yes, you can use this Skill to standardize Next.js metadata and OG image generation. It enforces performance and SEO configuration requirements, including next/image usage, next/font optimization, and proper script loading via next/script.

To fix hydration mismatches and server-incompatible package bundling issues in Next.js, this Skill enforces hydration safety rules and provides bundling fixes for server-incompatible packages, ensuring deterministic runtime selection between Node and Edge.