nextjs-rendering
/nextjs-rendering
Dobiera i wdraża strategie SSG, SSR, ISR, Streaming lub Partial Prerendering w Next.js App Router, w tym generateStaticParams i PPR.
- Autor
- HoangNguyen0403 ↗
- Repozytorium
- agent-skills-standard ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 22.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 7
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 22.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Dobiera i wdraża strategie SSG, SSR, ISR, Streaming lub Partial Prerendering w Next.js App Router, w tym generateStaticParams i PPR.
Oryginalny opis (EN)
Select and implement SSG, SSR, ISR, Streaming, or Partial Prerendering strategies in Next.js App Router. Use when choosing a rendering mode for a page, configuring generateStaticParams, or enabling PPR.
Jak działa
- Priority: P0 (CRITICAL)
- Workflow: Choose Rendering Strategy
- ISR with generateStaticParams Example
- Implementation Guidelines
- Anti-Patterns
- References
Podgląd SKILL.md
---
name: nextjs-rendering
description: Select and implement SSG, SSR, ISR, Streaming, or Partial Prerendering strategies in Next.js App Router. Use when choosing a rendering mode for a page, configuring generateStaticParams, or enabling PPR.
metadata:
triggers:
files:
- '**/page.tsx'
- '**/layout.tsx'
keywords:
- generateStaticParams
- dynamic
- dynamicParams
- PPR
- streaming
---
# Rendering Strategies (App Router)
## **Priority: P0 (CRITICAL)**
Choose rendering strategy based on data freshness and scaling needs. See [Strategy Matrix](references/strategy-matrix.md).
## Workflow: Choose Rendering Strategy
1. **Determine data freshness** — Static content? Use SSG. Periodic updates? Use ISR. Personalized? Use SSR.
2. **Configure fetch** — `force-cache` for SSG, `revalidate: N` for ISR, `no-store` for SSR.
3. **Add Suspense for streaming** — Wrap slow components in `<Suspense>` with fallback.
4. **Enable PPR if hybrid** — Set `ppr: true` in `next.config.js` for static shell + dynamic regions.
## ISR with generateStaticParams Example
See [implementation examples](references/implementation.md)
## Implementation Guidelines
- **SSG (Static Site Generation)**: Default for App Router. Use **`generateStaticParams`** to pre-render routes at build time. Triggered by **`fetch`** with **`cache: 'force-cache'`**.
- **SSR (Server-Side Rendering)**: Triggered by **`cookies()`**, **`headers()`**, or **`fetch`** with **`cache: 'no-store'`**. Use for personalized or high-freshness data.
- **ISR (Incremental Static Regeneration)**: Update static content after build. Use **`revalidate`** (time-based) or **`revalidatePath`** / **`revalidateTag`** (on-demand).
- **Streaming**: Use **`Suspense`** to wrap slow async components and prevent them from blocking initial page load. Use **`loading.tsx`** for route-level skeletons.
- **PPR (Partial Prerendering)**: Combine static shell with dynamic regions in single HTTP request. Enable **`ppr: true`** in `next.config.js`.
- **Strategies**: Choose rendering based on **SEO** (SSG/ISR) vs **Interactivity** (Client) vs **Personalization** (SSR). Utilize **`dynamicParams`** to control fallback behavior for uncached routes.
- **Hydration**: Avoid **Hydration Errors** by not using browser-only values (`window.innerWidth`, `Date.now()`) in initial render. Use **`mounted` useEffect pattern**.
- **Edge Runtime**: Use **`runtime: 'edge'`** for low-latency globally distributed execution where full Node.js APIs not required.
## Anti-Patterns
- **No root awaits in `page.tsx`**: Wrap slow components in `<Suspense>` to stream.
- **No SSR for static content**: Use SSG or ISR; reserve SSR for truly dynamic data.
- **No `typeof window` in initial render**: Use `useEffect` to avoid hydration errors.
## References
- [Strategy Selection Matrix](references/strategy-matrix.md)
- [Implementation Details](references/implementation-details.md)
- [Scaling Patterns](references/scaling-patterns.md)
Pliki w paczce (7)
- SKILL.md 3 KB
- evals/evals.json 2 KB
- references/SUSPENSE_BAILOUT.md 1 KB
- references/implementation-details.md 1 KB
- references/implementation.md 1 KB
- references/scaling-patterns.md 4 KB
- references/strategy-matrix.md 2 KB
Wersje
W bazie nie ma innych skilli o nazwie nextjs-rendering.
Migawka bazy z 13.11.2026 · wersja paczki 813670209b87 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100nextjs-data-fetching
Obsługuje pobieranie danych, buforowanie i rewalidację w Next.js App Router: wybór SSG, ISR, SSR lub streamingu per trasa, generateStaticParams, revalidateTag i Route Handlers. - 100nextjs-app-router-patterns
Prowadzi przez Next.js 14+ App Router: Server Components, streaming, trasy równoległe, pobieranie danych, SSR i SSG oraz optymalizację. - 100nextjs-ops
Obejmuje operacje w Next.js App Router: granicę serwer-klient, dwa modele cache, bezpieczeństwo Server Actions, streaming, proxy.ts i wdrożenie, w tym use cache, revalidateTag i PPR. - 91nextjs-data-fetching
Pomaga pobierać dane w Next.js za pomocą SSG, SSR i ISR przy budowie aplikacji opartych na danych. - 100nextjs-app-router-patterns
Pomaga pracować z Next.js 14+ App Router: Server Components, streaming, trasy równoległe, pobieranie danych, SSR i SSG oraz optymalizacja Server Components. - 100agent-next-js-expert
Wspiera aplikacje Next.js: App Router, Server Actions, middleware, ISR, SSR i SSG, optymalizację renderowania i wdrożenie na Vercel.