nextjs

Guide Next.js App Router implementations with rendering, data fetching, and caching rules.

16|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/JCETools-Petra/JCE-Opencode-Tools --skill nextjs-jcetools-petra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nextjs
Source: https://github.com/JCETools-Petra/JCE-Opencode-Tools/tree/main/config/skills/nextjs
Command: npx skills add https://github.com/JCETools-Petra/JCE-Opencode-Tools --skill nextjs-jcetools-petra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you design, implement, and verify Next.js (App Router/Pages Router) solutions that follow the platform’s rendering, data-fetching, caching, and boundary rules—reducing bugs caused by mismatched static vs dynamic behavior and incorrect Server/Client usage.

Core Features & Use Cases

  • Next.js rendering & caching strategy guidance: Choose between Static, ISR, Dynamic, PPR, and streaming patterns based on how the page’s content changes over time.
  • Data fetching and revalidation patterns: Use Server Components, Suspense, parallel fetch (Promise.all), tag-based revalidation, and explicit fetch caching controls for Next.js 15.
  • Safe architecture for UI and actions: Correctly separate Server Components from Client Components, implement Server Actions with input validation, and apply Route Handler/Middleware conventions.

Quick Start

Tell your AI exactly which Next.js route you are working on and what behavior you need (static/ISR/dynamic, data sources, and whether it needs interactivity), for example: “Review my app route implementation for caching and rendering correctness, propose the right rendering/data-fetch approach, and point out any Server/Client boundary mistakes.”

Frequently Asked Questions about nextjs

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

FAQPage Schema
How do I choose between static and dynamic rendering for Next.js App Router pages?

Choose Next.js rendering strategies by evaluating content volatility: static for fixed content, ISR for periodic updates, dynamic for real-time data, and streaming with Suspense for progressive loading.

What is the correct way to fetch data in Next.js 15 Server Components?

Fetch data in Next.js Server Components using parallel Promise.all requests with explicit caching opt-in controls and tag-based revalidation, ensuring correct static or dynamic behavior for your routes.

How do I separate Server Components from Client Components correctly in Next.js?

Separate Next.js components by keeping data fetching static on the server and pushing interactivity to the Client boundary, ensuring correct component architecture and avoiding mismatched rendering bugs.

How do I validate inputs for Next.js Server Actions?

Validate Next.js Server Action inputs explicitly on the server before processing interactive flows, ensuring data integrity and preventing unauthorized or malformed submissions from reaching your backend.

Does Next.js 15 require async params and searchParams in App Router?

Yes, Next.js 15 requires async params and searchParams in App Router, meaning page components must await these values before accessing them for dynamic route generation and data fetching.

Why are my Next.js fetch requests not caching data by default?

Next.js 15 uses fetch caching opt-in behavior, meaning requests are uncached by default unless you explicitly define caching controls, preventing unintended static data retention across dynamic routes.