next-best-practices

Enforce Next.js best-practice patterns across App Router codebases.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/not-ani/elevated-school-takehome --skill next-best-practices-not-ani
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: next-best-practices
Source: https://github.com/not-ani/elevated-school-takehome/tree/main/.agents/skills/next-best-practices
Command: npx skills add https://github.com/not-ani/elevated-school-takehome --skill next-best-practices-not-ani

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conveys comprehensive Next.js best-practices to standardize project structure and improve reliability across teams.

Core Features & Use Cases

  • File conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, and bundling guidance for Next.js apps.
  • Use cases include onboarding new engineers, code reviews, and refactoring sessions to align with recommended patterns.

Quick Start

Review a Next.js project and apply the documented best practices to improve structure, routing, and performance.

Frequently Asked Questions about next-best-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are the best practices for Next.js App Router structure and server components?

Next.js App Router best practices enforce proper React Server Component boundaries, file conventions, and data patterns to improve project maintainability and reliability. They standardize routing structure across teams.

How do I optimize images and fonts in a Next.js application?

Optimize Next.js images and fonts by applying documented asset optimization and bundling guidelines. This ensures proper loading strategies and performance improvements across the codebase.

Does this Next.js best practices guidance cover route handlers and error handling?

Yes, Next.js best practices guidance covers route handlers, error handling, and metadata usage. It aligns projects with documented rules for reliable data fetching and API route management.

When do I need to standardize Next.js metadata usage and async APIs?

Standardize Next.js metadata usage and async APIs during onboarding, code reviews, or refactoring sessions. This ensures engineers align with recommended patterns for data fetching and SEO configuration.

What is the best way to review a Next.js project for recommended patterns?

The best way to review a Next.js project is to audit its structure against documented best practices for routing, server components, and bundling. This identifies areas to improve performance and reliability.