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