Update Docs

Update Docs is an official skill from Vercel’s Next.js repository. According to the provider, it helps derive documentation work from changes on the active Next.js branch, locate the relevant documentation pages, and prepare updates to Markdown and MDX files in a structured way. The originally supplied .claude/skills/update-docs path is not a standalone reachable directory in the current canary branch because .claude/skills points to .agents/skills. The verified primary source is therefore .agents/skills/update-docs. This skill is operating guidance for compatible coding agents, not an independent documentation system, not a Next.js compiler, and not a guarantee that an editorial change is complete or technically correct.

Purpose and triggers

The guidance is intended for pull requests or local changes that may affect documentation. Typical triggers include requests to update documentation for changes, check which pages belong to a pull request, synchronize docs with code, scaffold documentation for a feature, or review the completeness of existing text. The workflow starts with a summary of branch changes. The agent then maps affected source paths to likely documentation areas. Components, server functions, build code, shared libraries, and configuration changes lead to different kinds of documentation work.

Connecting code with documentation

A central benefit of the skill is its relationship between source code and the documentation structure. The included reference maps client components, server functions, configuration, file conventions, directives, metadata, and CLI commands. A change to a public function should be investigated in the API reference, while a new concept usually belongs in a guide. Before editing, the agent should read the existing page, understand its frontmatter and structure, and search for shared content between the App Router and Pages Router. When a Pages Router page uses a source field that points to the App Router page, the shared origin should be edited so that duplicate copies do not drift apart.

Writing and validation conventions

According to the provider, MDX pages need frontmatter containing title and description. The guidance describes kebab-case names, suitable directories for components, functions, configuration, guides, and file conventions, plus related links for next steps. TypeScript examples come before JavaScript variants and use the intended switcher structure. Router-specific material is separated with AppOnly or PagesOnly. An agent should also respect the repository’s official Next.js conventions, avoid unnecessary duplication, and run the repository’s documented linting checks for formatting. Deciding which technical statement accurately explains an API remains a human editorial and engineering responsibility.

Boundaries and security

The skill can prepare documentation changes, but it does not replace code review or maintainer expertise. A mapping is a useful lead, not proof that every affected page has been found. The workflow asks for user confirmation before individual edits. That reduces unintended changes but does not eliminate the risk of incorrect assumptions, stale examples, or accidental edits to shared files. During execution, an agent may read source code, logs, configuration, and MDX content that contains sensitive information. Tokens, credentials, private environment values, and internal material must not be placed in skill text, prompts, or commit history. Local editing does not automatically mean that content stays outside the selected agent and model provider’s processing path.

Context and source quality

The official Next.js documentation explains how to contribute to the documentation, while Vercel documentation describes Next.js on the Vercel platform. These sources complement the concrete skill file but do not replace it as the description of this workflow. The Next.js repository identifies the MIT license. This entry does not claim that the skill automatically supports every Next.js version, documentation layout, or external agent. Teams should check the branch, source paths, frontmatter, examples, and published pages against the current repository state before merging. Current provider terms and capabilities should be checked directly with Vercel and Next.js; this entry states no concrete prices.