Skip to content
agent-skills

nextjs

Pack path: nextjs/

Skills

Section titled “Skills”
  • Next.js Data Fetching and Cache — Fetch data and control cache behavior in Next.js App Router. Use when tasks mention fetch in Server Components, request memoization, cache components, use cache, unstable_cache, revalidatePath, revalidateTag, updateTag, generateStaticParams, route-segment cache behavior, or deciding whether a route should stay static, dynamic, or revalidated.
  • Next.js Metadata, SEO, and File Conventions — Manage metadata and SEO surfaces in Next.js App Router. Use when tasks mention metadata, generateMetadata, generateViewport, ImageResponse, Open Graph or Twitter images, robots.txt, sitemap.xml, manifest.json, JSON-LD, canonical URLs, or deciding between metadata exports and metadata file conventions.
  • Next.js Overview and App Router — Set up Next.js App Router, choose the right starting path, and route work to the correct follow-up Next.js skill. Use when tasks mention create-next-app, App Router installation, project structure, layouts, pages, linking, navigation, Server vs Client Components, path aliases, src/app, App Router vs Pages Router decisions, or Next.js version and upgrade questions.
  • Next.js Performance And Render Cost — Use when a Next.js App Router route is slow because of render cost, client bundle weight, hydration work, or weak server-client boundaries. Covers server-first rendering, client boundary minimization, route cost diagnosis, and avoiding fashionable but expensive patterns.
  • Next.js Rendering Runtime and Middleware — Choose rendering mode and request runtime boundaries in Next.js App Router. Use when tasks mention Server vs Client Components, static vs dynamic rendering, streaming, route segment config, runtime = 'edge', Node.js vs Edge decisions, or legacy middleware questions that now map to proxy.ts.
  • Next.js Server Actions and Route Handlers — Build safe mutation and API boundaries in Next.js App Router. Use when tasks mention use server, Server Functions, Server Actions, Route Handlers, route.ts, form action, formAction, cookies, redirects after mutations, request and response handling, or deciding between UI-driven mutation flow and explicit HTTP endpoints.