nextjs-rendering-strategy
npx skills add https://github.com/natemcgrady/skills --skill nextjs-rendering-strategy
Agent 安装分布
Skill 文档
Next.js Rendering Strategy
Goal
Produce a per-route rendering plan optimizing for: SEO/share previews, data freshness, personalization/auth, latency (TTFB/LCP), compute cost, and build-time scale.
References
Load these as needed:
- decision-framework.md â Strategy definitions, quick decision checklist, heuristics matrix, edge cases/pitfalls. Load when deciding strategy for any route.
- implementation-patterns.md â Code snippets for App Router and Pages Router. Load when producing implementation output.
- archetypes.md â Common site archetypes (marketing, blog, e-commerce, SaaS) with pre-mapped strategies. Load to quickly map familiar route types.
Analysis Process
Step 0 â Inventory routes
- App Router:
app/**/page.tsx,app/**/layout.tsx - Pages Router:
pages/**/*.tsx
For each route, note: path, auth requirement, data sources, update frequency, SEO requirement, personalization, and scale (number of dynamic pages).
Step 1 â Classify by cacheability
- Public cacheable â same HTML for all users
- Public query-dependent â search/filters vary output
- User-specific â cannot share cache across users
- Mixed â public shell + personalized widgets
Step 2 â Classify by freshness SLA
- Static OK â days/weeks
- Bounded staleness OK â minutes/hours
- Real-time required â seconds/always current
Step 3 â Apply the strategy matrix
See decision-framework.md for the full matrix and heuristics.
Step 4 â Validate against build/compute constraints
- Huge cardinality (millions of pages) â avoid prebuilding all; use ISR on-demand or SSR for long-tail
- SSR compute too high â prefer ISR where possible, or edge caching (only if safe)
Step 5 â Produce the final plan
For each route output:
- Chosen strategy
- Why (1â3 bullets)
- Data freshness SLA
- Caching notes
- Implementation snippets (see implementation-patterns.md)
Required Output
1. Route Plan Table
| Route | Audience | Freshness SLA | SEO | Strategy | Notes |
|---|
2. Top 5 Highest Impact Changes
For each: what to change, expected benefit (latency/cost/SEO/freshness), risks.
3. Implementation Checklist
Files to edit, strategy-specific config/snippets, how to validate (TTFB, LCP, cache hit rate, correctness).
Validation Signals (after changes)
Measure per route: TTFB, LCP, cache hit rate, serverless compute time/invocations, staleness incidents, SEO crawl/index correctness.