with one click
nextjs-rendering
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.
Menu
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.
| 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"]}} |
Choose rendering strategy based on data freshness and scaling needs. See Strategy Matrix.
force-cache for SSG, revalidate: N for ISR, no-store for SSR.<Suspense> with fallback.ppr: true in next.config.js for static shell + dynamic regions.generateStaticParams to pre-render routes at build time. Triggered by fetch with cache: 'force-cache'.cookies(), headers(), or fetch with cache: 'no-store'. Use for personalized or high-freshness data.revalidate (time-based) or revalidatePath / revalidateTag (on-demand).Suspense to wrap slow async components and prevent them from blocking initial page load. Use loading.tsx for route-level skeletons.ppr: true in next.config.js.dynamicParams to control fallback behavior for uncached routes.window.innerWidth, Date.now()) in initial render. Use mounted useEffect pattern.runtime: 'edge' for low-latency globally distributed execution where full Node.js APIs not required.page.tsx: Wrap slow components in <Suspense> to stream.typeof window in initial render: Use useEffect to avoid hydration errors.Standardize BRD and BRD-lite discovery for business goals, stakeholder impact, current-to-future state, and measurable value outcomes. Use when creating BRD, business case, project justification, ROI narrative, or AS-IS to TO-BE scope.
Standardize PRD discovery and drafting for product scope, user outcomes, requirement IDs, and acceptance criteria. Use when creating PRD, product requirements, feature specification, or acceptance criteria plan.
Standardize SRS and FRS specifications for technical behavior, interfaces, data contracts, quality constraints, and verification mapping. Use when writing SRS, functional specification, system behavior requirements, API/data contracts, or non-functional thresholds.
Clarify a rough product or engineering idea into a BRD-lite brief (Why) with measurable business value.
Turn an approved PRD or implementation goal into SRS/FRS technical requirements (How), architecture, contracts, and verification decisions.
Plan a feature from BRD-lite brief or clear intent into PRD (What), decisions, implementation plan, and task slices.