Qstash JS
upstash/qstash-js
Work with the QStash JavaScript/TypeScript SDK for serverless messaging, scheduling.
Next.js 16 App Router pages mixing static and dynamic content — Partial Prerendering (PPR) under the Cache Components model.
Install Nextjs Ppr Patterns
$ npx skills add pproenca/dot-skills --skill nextjs-ppr-patterns -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pproenca/dot-skills nextjs-ppr-patterns --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.experimental/nextjs-ppr-patterns .claude/skills/nextjs-ppr-patterns && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "nextjs-ppr-patterns" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/nextjs-ppr-patterns into .claude/skills/nextjs-ppr-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nextjs-ppr-patterns", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/nextjs-ppr-patternsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pproenca/dot-skills --skill nextjs-ppr-patterns -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pproenca/dot-skills nextjs-ppr-patterns --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.experimental/nextjs-ppr-patterns .agents/skills/nextjs-ppr-patterns && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "nextjs-ppr-patterns" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/nextjs-ppr-patterns into .agents/skills/nextjs-ppr-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nextjs-ppr-patterns", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pproenca/dot-skills --skill nextjs-ppr-patterns -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pproenca/dot-skills nextjs-ppr-patterns --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.experimental/nextjs-ppr-patterns .cursor/skills/nextjs-ppr-patterns && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "nextjs-ppr-patterns" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/nextjs-ppr-patterns into .cursor/skills/nextjs-ppr-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nextjs-ppr-patterns", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pproenca/dot-skills.git --path skills/.experimental/nextjs-ppr-patterns--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pproenca/dot-skills --skill nextjs-ppr-patterns -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pproenca/dot-skills nextjs-ppr-patterns --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.experimental/nextjs-ppr-patterns .gemini/skills/nextjs-ppr-patterns && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "nextjs-ppr-patterns" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/nextjs-ppr-patterns into .gemini/skills/nextjs-ppr-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nextjs-ppr-patterns", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pproenca/dot-skills nextjs-ppr-patternsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pproenca/dot-skills --skill nextjs-ppr-patterns -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.experimental/nextjs-ppr-patterns .github/skills/nextjs-ppr-patterns && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "nextjs-ppr-patterns" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/nextjs-ppr-patterns into .github/skills/nextjs-ppr-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nextjs-ppr-patterns", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pproenca/dot-skills --skill nextjs-ppr-patterns -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pproenca/dot-skills nextjs-ppr-patterns --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.experimental/nextjs-ppr-patterns .opencode/skills/nextjs-ppr-patterns && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "nextjs-ppr-patterns" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/nextjs-ppr-patterns into .opencode/skills/nextjs-ppr-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nextjs-ppr-patterns", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
nextjs-ppr-patterns- GitHub stars
- 214
- Token cost
- ~2.3k tokens
- SKILL.md length
- 821 words
- Files
- 27 (incl. references, assets)
- Skills in repo
- 182
- Repo updated
- First seen
- Licence
- MIT
At a glance
Next.js 16 App Router pages mixing static and dynamic content — Partial Prerendering (PPR) under the Cache Components model.
- Works in 6 steps: Setup & Mental Model → The Suspense Boundary → Caching with 'use cache' → …
- CacheComponents
- SKILL.md covers When to Apply, Rule Categories, Quick Reference and How to Use, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Nextjs Ppr Patterns is an agent skill from pproenca/dot-skills. Next.js 16 App Router pages mixing static and dynamic content — Partial Prerendering (PPR) under the Cache Components model. Covers enabling it with cacheComponents (the removed experimental.ppr / experimentalppr flags), the dynamic-by-default rendering inversion, the Suspense static-shell/dynamic-hole boundary, the 'use cache' directive (automatic keys, cacheLife/cacheTag, children/action pass-through, runtime values as props, serverless durability), async runtime APIs and connection() for non-determinism, page…
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 29 other files, including reference files and assets (for example `AGENTS.md`, `assets/templates/_template.md` and `metadata.json`).
It sits in Backend & APIs, covering Serverless. It works with Next.js. The repository describes itself as: A collection of AI agent skills following the Agent Skills open format. The licence is MIT.
When your agent uses it
- CacheComponents
- Suspense streaming
- Partial prerendering
- Static-shell work even when not named explicitly
Example prompts
- “use cache”
- “/nextjs-ppr-patterns”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cf93c57. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
nextjs.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Nextjs Ppr Patterns loads about 2.3k tokens when it runs, and up to ~13k if it reads all its reference files. Until then it costs about 219 tokens; SKILL.md has 821 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from pproenca/dot-skills at commit cf93c57, republished under its MIT licence (© pproenca). 821 words, ~2,334 tokens.
Download SKILL.mdSave it as
.claude/skills/nextjs-ppr-patterns/SKILL.md (or your agent's skills folder). This skill also uses 26 other files; get the full folder from GitHub.- name
- nextjs-ppr-patterns
- description
- Next.js 16 App Router pages mixing static and dynamic content — Partial Prerendering (PPR) under the Cache Components model. Covers enabling it with cacheComponents (the removed experimental.ppr / experimental_ppr flags), the dynamic-by-default rendering inversion, the Suspense static-shell/dynamic-hole boundary, the 'use cache' directive (automatic keys, cacheLife/cacheTag, children/action pass-through, runtime values as props, serverless durability), async runtime APIs and connection() for non-determinism, page composition from a single hole to parallel dashboards to streaming a Promise into a Client Component with use(), and forms/wizards with updateTag read-your-writes and Activity state preservation. Triggers on PPR, cacheComponents, 'use cache', Suspense streaming, partial prerendering, or static-shell work even when not named explicitly.
Next.js 16 Partial Prerendering Patterns
Partial Prerendering (PPR) for the Next.js 16 App Router under the Cache Components model — the decisions PPR forces and how to settle them, written so an agent applies them while writing or reviewing code. Contains 21 rules across 6 categories, ordered from easy to complex: enable PPR → understand the static/dynamic boundary → cache → handle runtime data → compose whole pages → build forms and wizards. Each rule corrects a specific wrong default of a model defaulting to Next.js 14/15; there is no rule for things the model already gets right.
Version-specific. This skill targets Next.js 16 (PPR via
cacheComponents, React 19.2). The Next.js 14/15experimental.pprflag andexport const experimental_pprroute export were removed — seesetup-enable-cache-components. For migrating an existing app, see the migration guide.
Write, then verify. These rules are for authoring PPR; they can't tell you what actually rendered. To empirically deconstruct the boundary — diff the static shell against the hydrated DOM to find the dynamic holes, locate the
'use client'islands, measure loading, and explain why a route is dynamic — drivenext buildand a real browser per _debug-boundaries.md.
When to Apply
- Building or reviewing a Next.js 16 page that mixes static chrome with personalized, real-time, or per-request content
- Enabling or migrating PPR (
cacheComponents), or seeing deadexperimental.ppr/experimental_pprcode - Deciding where
<Suspense>boundaries go, or debugging anUncached data was accessed outside of <Suspense>build error - Adding
'use cache',cacheLife,cacheTag, or choosingupdateTag/revalidateTag/refreshafter a mutation - Composing forms, multi-step wizards, dashboards, or streaming server data into interactive Client Components
- Empirically verifying or debugging what actually rendered — which parts are in the static shell vs streamed, where the CSR/SSR boundary is, and why a route went dynamic
Rule Categories
| # | Category | Prefix | Covers |
|---|---|---|---|
| 1 | Setup & Mental Model | setup- | Enabling PPR with cacheComponents; the removed experimental flags; dynamic-by-default / opt-in caching inversion |
| 2 | The Suspense Boundary | shell- | <Suspense> as the static/dynamic seam; the build error; boundary granularity; what Suspense does not do |
| 3 | Caching with 'use cache' | cache- | Directive levels; automatic keys; runtime values as props; pass-through; cacheLife/cacheTag; serverless durability |
| 4 | Runtime APIs & Non-Determinism | runtime- | Async request APIs forcing a boundary; generateStaticParams; connection() for randomness/time |
| 5 | Page Composition Recipes | compose- | Single hole → parallel dashboard → Promise + use() streaming → not opting the whole app out of the shell |
| 6 | Forms, Mutations & Wizards | mutate- | updateTag vs revalidateTag vs refresh; URL-driven wizard steps; <Activity> field preservation |
Quick Reference
1. Setup & Mental Model
setup-enable-cache-components— Enable PPR viacacheComponents: true; theexperimental.ppr/experimental_pprflags are removedsetup-dynamic-by-default— Everything renders at request time; caching is opt-in via'use cache'(andfetchis no longer cached)
2. The Suspense Boundary
shell-suspense-is-the-boundary—<Suspense>is the static-shell/dynamic-stream seam, not a spinnershell-wrap-uncached-data— Uncached/runtime reads must be wrapped (or'use cache'd) or the build errorsshell-suspense-does-not-force-dynamic— Suspense alone does not make synchronous work dynamicshell-place-boundaries-low— Wrap the dynamic leaf, not the whole page, so the shell stays large
Show full SKILL.md (339 more words)Show less
3. Caching with 'use cache'
cache-use-cache-directive— Mark static/cacheable work at the function / component / page / layout / file levelcache-keys-are-automatic— Arguments and closures form the cache key; pass varying inputs as argscache-pass-runtime-values-as-props— You can't readcookies()/headers()inside a cached scope; pass values incache-pass-through-children-and-actions— Pass dynamicchildrenand Server Actions through a cached component untouchedcache-set-lifetime-and-tags—cacheLifecontrols TTL,cacheTagenables on-demand invalidationcache-in-memory-not-durable-serverless— In-memory cache isn't durable on serverless; use'use cache: remote'
4. Runtime APIs & Non-Determinism
runtime-request-apis-force-a-boundary— Asynccookies/headers/searchParams/paramsforce a dynamic boundaryruntime-keep-param-routes-static—generateStaticParamskeeps[slug]routes in the static shellruntime-gate-nondeterminism-with-connection— GateMath.random/Date.now/cryptobehindconnection(), or cache the value
5. Page Composition Recipes
compose-single-dynamic-hole— The baseline: static shell + one<Suspense>holecompose-parallel-holes— One boundary per widget → parallel streaming, no waterfallcompose-stream-to-client-with-use— Pass an un-awaited Promise and unwrap withuse()in a Client Componentcompose-do-not-opt-out-the-shell— Don't defer the whole app to silence a boundary error
6. Forms, Mutations & Wizards
mutate-updatetag-vs-revalidatetag—updateTag(read-your-writes) vsrevalidateTag(tag, profile)(SWR) vsrefresh()mutate-wizard-url-driven-steps— URL-driven steps + static chrome +<Activity>field preservation
How to Use
Read a reference file when its decision comes up. Each rule names the wrong default it corrects, then shows the canonical way (with an incorrect/correct contrast only where the wrong way is a real trap). If you're starting cold, read setup- first — the rest assumes the dynamic-by-default mental model.
- Section definitions — category structure and ordering
- Boundary debugging — empirically deconstruct the static/dynamic boundary and loading with
next buildand chrome-devtools-mcp (via mcporter); use it when a PPR result surprises you or you're chasing ablocking-routeerror - Rule template — for adding new rules
- AGENTS.md — auto-built table of contents across all rules
Related Skills
nextjs— broader Next.js 16 App Router best practices (caching, server components, routing, hygiene)opinionated-nextjs-patterns— full opinionated architecture (data layer, mutations, client boundaries) that uses these PPR patternsreact-fetch-cache-patterns— request orchestration and client-side caching for data-heavy React UIs
Reference Files
| File | Description |
|---|---|
| references/_sections.md | Category definitions and ordering |
| references/_debug-boundaries.md | Empirical CSR/SSR boundary & loading debugging (next build + chrome-devtools-mcp via mcporter) |
| assets/templates/_template.md | Template for new rules |
| metadata.json | Version and source references |
© pproenca, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 26 other files (references, assets) in skills/.experimental/nextjs-ppr-patterns of pproenca/dot-skills.
- SKILL.md
- AGENTS.md
- assets/templates/_template.md
- metadata.json
- references/_debug-boundaries.md
- references/_sections.md
- references/cache-in-memory-not-durable-serverless.md
- references/cache-keys-are-automatic.md
- references/cache-pass-runtime-values-as-props.md
- references/cache-pass-through-children-and-actions.md
- references/cache-set-lifetime-and-tags.md
- references/cache-use-cache-directive.md
- references/compose-do-not-opt-out-the-shell.md
- references/compose-parallel-holes.md
- references/compose-single-dynamic-hole.md
- references/compose-stream-to-client-with-use.md
- references/mutate-updatetag-vs-revalidatetag.md
- references/mutate-wizard-url-driven-steps.md
- … and 9 more
Open the folder on GitHubat commit cf93c57
Compare with similar skills
Nextjs Ppr Patterns next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Nextjs Ppr Patterns this skillpproenca/dot-skills | 214 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Qstash JSupstash/qstash-js | 269 | 1 repos | ~746 | Automated safety check: Pass | MIT | |
| Nextjs Ssrasmyshlyaev177/test-proxy-recorder | 112 | — | ~4.4k | Automated safety check: Pass | MIT | |
| Edgeone Pages Website SkeletonTencentEdgeOne/awesome-website-prompts-and-skills | 183 | — | ~2.2k | Automated safety check: Notes | MIT | |
| Deploy Verceljohnku2011/boilerplates-with-ai-skills | 240 | — | ~660 | Automated safety check: Notes | MIT | |
| Inngestpedronauck/skills | 633 | 4 repos | ~3.1k | Automated safety check: Pass | None |
Similar skills
- Official
Nextjs Ssr
asmyshlyaev177/test-proxy-recorder
Tag server-side fetches with the x-test-rcrd-id session header so SSR is recorded under the correct Playwright test session.
Edgeone Pages Website Skeleton
TencentEdgeOne/awesome-website-prompts-and-skills
基于 EdgeOne Pages 的全栈网站生成方案。用户说一句话（如「帮我建一个电商站」「做一个AI客服站」「做个管理后台」），AI 自动组合 Auth、Cart、Payment、AI Chat、Admin 五大模块，生成完整 Next.js 前后端代码并部署到 EdgeOne Pages 全球 CDN。支持电商、AI 助手、SaaS 管理后台三大模板。底层使用 Edge…
Deploy Vercel
johnku2011/boilerplates-with-ai-skills
A skill your agent uses when deploying or configuring this project on Vercel — env vars, build settings, serverless limits, and production checks for Next.js or Express.
Inngest
pedronauck/skills
Inngest expert for serverless-first background jobs, event-driven workflows, and durable execution without managing queues or workers.
- Official
Upstash Redis
github/awesome-copilot
Use Redis over HTTP from serverless and edge runtimes with @upstash/redis, and add rate limiting with @upstash/ratelimit.
More from pproenca/dot-skills
All 182 skills in this repoAudio Voice Recovery
pproenca/dot-skills
Audio forensics and voice recovery guidelines for CSI-level audio analysis.
Codemod React Pipeline
pproenca/dot-skills
Guided, scripted pipeline for running JSX/TSX/React codemods safely across large legacy codebases.
Dev Rfc
pproenca/dot-skills
Create well-structured RFCs and technical proposals for software projects.
Dx Harness
pproenca/dot-skills
Developer-experience friction auditing and fixing — slow onboarding, repeated manual setup steps, missing bootstrap/reset/seed scripts, undiscoverable conventions.
Language Spec Author
pproenca/dot-skills
Turn a rough idea for a language into a complete, implementable specification — a DSL, query, config/data, template, or protocol language — by interviewing the author dimension by dimension until…
Python Pep Author
pproenca/dot-skills
Drafting Python Enhancement Proposals (PEPs) — proposing a Python language feature, a standard library change, an interoperability standard, or an informational/process document for the Python…
Related
Works with
Categories
Questions about Nextjs Ppr Patterns
What does Nextjs Ppr Patterns do?
Next.js 16 App Router pages mixing static and dynamic content — Partial Prerendering (PPR) under the Cache Components model. Nextjs Ppr Patterns is an agent skill from pproenca/dot-skills.js 16 App Router pages mixing static and dynamic content — Partial Prerendering (PPR) under the Cache Components model.
When should I use Nextjs Ppr Patterns?
Nextjs Ppr Patterns fits situations like: cacheComponents; suspense streaming; partial prerendering; static-shell work even when not named explicitly.
How do I install Nextjs Ppr Patterns in Claude Code?
Run `npx skills add pproenca/dot-skills --skill nextjs-ppr-patterns -a claude-code`. Or copy the skill folder (skills/.experimental/nextjs-ppr-patterns in pproenca/dot-skills) into .claude/skills/nextjs-ppr-patterns in your project. Claude Code loads it when a task matches its description.
How do I install Nextjs Ppr Patterns in Codex?
Run `npx skills add pproenca/dot-skills --skill nextjs-ppr-patterns -a codex`. Or copy the skill folder (skills/.experimental/nextjs-ppr-patterns in pproenca/dot-skills) into .agents/skills/nextjs-ppr-patterns in your project. Codex loads it when a task matches its description.
Can I use Nextjs Ppr Patterns in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pproenca/dot-skills --skill nextjs-ppr-patterns -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nextjs-ppr-patterns, .gemini/skills/nextjs-ppr-patterns, .github/skills/nextjs-ppr-patterns and .opencode/skills/nextjs-ppr-patterns in your project.
What does Nextjs Ppr Patterns need to run?
SKILL.md names no scripts, command-line tools or credentials: Nextjs Ppr Patterns is instructions for the agent only.
Does Nextjs Ppr Patterns access the network?
SKILL.md names 1 domain. As links in the text: nextjs.org. This is read from the text; nothing was executed.
Is Nextjs Ppr Patterns safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Nextjs Ppr Patterns use?
Nextjs Ppr Patterns is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Nextjs Ppr Patterns use?
About 2.3k tokens (SKILL.md is roughly 9.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 11k tokens, read only when the agent opens those files.
What are the alternatives to Nextjs Ppr Patterns?
Skills that share tags, products or a category with Nextjs Ppr Patterns: Qstash JS (upstash/qstash-js, 269 stars), Nextjs Ssr (asmyshlyaev177/test-proxy-recorder, 112 stars), Edgeone Pages Website Skeleton (TencentEdgeOne/awesome-website-prompts-and-skills, 183 stars) and Deploy Vercel (johnku2011/boilerplates-with-ai-skills, 240 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Nextjs Ppr Patterns?
pproenca (a GitHub user) maintains it in pproenca/dot-skills, which has 214 GitHub stars. The repository holds 182 skills in this directory. The repository was last updated on August 15, 2026.
Source: pproenca/dot-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.