React Sync · vercel/next.js · Skills Docs

Credited skills

Skill 23 of 24

React Sync

Build local React changes in the bundle variants consumed by Next.js, sync them into a local Next.js checkout, and test the resulting integration.

1 minute · 174 words · 3 sections

Sync React to Next.js

Use this skill when syncing a local React checkout into this Next.js checkout.

Build and sync

Build React from its own checkout. Pass this skill’s script by its absolute path, because the working directory must be the React repository.
```
cd <react-repo>
bash <next-repo>/.agents/skills/react-sync/scripts/build-for-next.sh
```
This creates build/oss-stable and build/oss-experimental with the bundle variants that Next.js consumes.

Sync the build into Next.js:

cd <next-repo>
PATH="$(dirname "$(command -v corepack)"):$PATH" \
  pnpm sync-react

$react-vendoring - vendored React runtime and type boundaries after syncing.

Appendix 23.1

1 file · 964 B

Everything this skill ships beside its prose. All of it is set here, as a subchapter of skill 23.

ScriptsShell · 1 file

Executable code the skill can run.

23.1Build For Nextscripts/build-for-next.sh964 B

Credited

This skill is installed in vercel/next.js — in use here rather than published from here — so there is no install command for it on this page.

About this skill

Trigger

Build local React changes in the bundle variants consumed by Next.js, sync them into a local Next.js checkout, and test the resulting integration. Use when working on React changes that need validation in Next.js, or when asked to run buildForNext, pnpm sync-react, or synchronize a React checkout with Next.js.

The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/vercel/next.js, branch canary, last pushed 28 August 2026.

Licence

MIT — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

24 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 2 distinct layouts observed: .agents/skills/*/SKILL.md, skills/*/SKILL.md.

Authorship

6 of 24 skills are installed into the repository rather than published from it. They are shelved in the closing “Credited skills” part and remain the work of their own authors. A skill counts as credited when its only copy lives under one agent’s dot directory; visible directories, per-agent mirror sets, and skills installable from this repository on skills.sh all count as published.

Issue colours

Resolved from the owner’s published design.md — hue 2°, chroma 0.190. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Shifted “3 headings” from h1 to h2 so the skill title is the only h1.

Spec compliance

Every skill satisfies the Agent Skills specification’s frontmatter rules.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .claude-plugin/marketplace.json by Vercel, declaring 1 plugin. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Sync React to Next.js

Build and sync

Related Skills

Appendix 23.1

ScriptsShell · 1 file

About this skill

Trigger

Colophon

Appendix 23.1

ScriptsShell · 1 file