Next.js framework skill (v16.2 canary)
Next.js reference distilled from the official docs — file-system routing, Server vs Client Components, navigation, data fetching, caching and revalidation, Server Actions, file conventions, and built-in components
- What
- Next.js reference distilled from the official docs — file-system routing, Server vs Client Components, navigation, data fetching, caching and revalidation, Server Actions, file conventions, and built-in components
- Cost
- Free
- Needs
- a Next.js project the agent can read and work on — the skill is a distilled docs reference, not software to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @hairyf's Next.js skill: a framework reference generated from the official Next.js documentation (generation scripts by antfu/skills — credited in the source file), based on Next.js v16.2.0-canary.16 (January 2026). Covers file-system routing (folders, layouts, pages), Server vs Client Components, navigation (linking, prefetching, transitions), data fetching in server and client components, streaming with Suspense, caching strategies (fetch caching, tags, revalidation), Server Actions for mutations, file conventions (dynamic routes, loading.tsx, error.tsx), and built-in components (Link, Image, Script, Font) — each topic pointing to a focused `references/*.mdx` doc. Honest caveats: a distilled docs reference, not hands-on tooling — the agent needs a Next.js project to apply it to; generated against a canary release, so verify anything that looks newer than your installed version. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a Next.js project the agent can read and work on — the skill is a distilled docs reference, not software to install Install "Next.js framework skill (v16.2 canary)" for me. It gives my agent @hairyf's Next.js reference: file-system routing (folders, layouts, pages), Server vs Client Components, navigation (linking, prefetching, transitions), data fetching in server and client components, streaming with Suspense, caching strategies (fetch caching, tags, revalidation), Server Actions for mutations, file conventions (dynamic routes, loading.tsx, error.tsx), and built-in components (Link, Image, Script, Font) — each topic in a focused references/*.mdx doc. Generated from the official Next.js docs (antfu/skills generation scripts), based on v16.2.0-canary.16. MIT-licensed. Repository: https://github.com/hairyf/skills/blob/main/skills/next/SKILL.md 1. Fetch the SKILL.md file (and the references/ folder) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and references for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "next". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at my Next.js project; nothing else — it's a reference). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.