next-best-practices

스타1

포크0

업데이트2026년 4월 1일 20:38

Next.js App Router best practices for routing, data fetching, rendering, and optimization.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

RevealUIStudio

RevealUIStudio/revcon

다운로드

Next.js Best Practices

Refer to the official documentation for comprehensive guidance:

Use Server Components by default; add 'use client' only when the component needs browser APIs, event handlers, or React hooks like useState/useEffect
In Next.js 15+, params, searchParams, cookies(), and headers() are async -- always await them
Avoid data waterfalls by parallelizing fetches with Promise.all or leveraging Suspense boundaries to stream independent sections
Use generateMetadata for dynamic SEO metadata and next/image with explicit width/height or sizes for all images
Prefer Server Actions ('use server') for mutations over client-side API calls to Route Handlers

이 저장소의 다른 Skills

같은 저장소

Create and apply Drizzle ORM migrations against the single Neon-primary PostgreSQL database

Run the 15-check pre-launch preflight and interpret results with context-aware fix suggestions

Next.js Cache Components, 'use cache' directive, PPR, cacheLife, cacheTag, and migration from unstable_cache.

Turborepo monorepo task orchestration, caching, and pipeline configuration guidance.

React composition patterns for building maintainable, reusable component architectures.

Deployment to Vercel including configuration, environment variables, and production best practices.

name	next-best-practices
description	Next.js App Router best practices for routing, data fetching, rendering, and optimization.

Refer to the official documentation for comprehensive guidance:

Use Server Components by default; add 'use client' only when the component needs browser APIs, event handlers, or React hooks like useState/useEffect
In Next.js 15+, params, searchParams, cookies(), and headers() are async -- always await them
Avoid data waterfalls by parallelizing fetches with Promise.all or leveraging Suspense boundaries to stream independent sections
Use generateMetadata for dynamic SEO metadata and next/image with explicit width/height or sizes for all images
Prefer Server Actions ('use server') for mutations over client-side API calls to Route Handlers