docs: present each Skill as steps in the AI agents guide - #96751

Each Skill section was a prose paragraph that assumed you had read the
ones above it. Reframe the three shipped Skills as a lead sentence,
three steps, and a linked prerequisite, so landing on an anchor from
search is enough.

Also drops the claim that the optimizer makes a route instant. It works
one navigation toward the UI you decide should be there, and commits the
passing test with the refactoring.

<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

We encourage you to use AI to assist you in researching, creating, and
reviewing changes. However, you must review and deeply understand the
contributions you are making. For this reason, **pull request
descriptions from external contributors must be written by a human**.

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Signed commits

- This repository requires verified commit signatures on protected
branches.
- If this pull request is blocked for unsigned commits, re-sign the
commits and force-push the branch.
- A `Signed-off-by` line in the commit message is not enough.

## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

Each Skill section was a prose paragraph that assumed you had read the
ones above it. Reframe the three shipped Skills as a lead sentence,
three steps, and a linked prerequisite, so landing on an anchor from
search is enough.

Also drops the claim that the optimizer makes a route instant. It works
one navigation toward the UI you decide should be there, and commits the
passing test with the refactoring.

<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

We encourage you to use AI to assist you in researching, creating, and
reviewing changes. However, you must review and deeply understand the
contributions you are making. For this reason, **pull request
descriptions from external contributors must be written by a human**.

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Signed commits

- This repository requires verified commit signatures on protected
branches.
- If this pull request is blocked for unsigned commits, re-sign the
commits and force-push the branch.
- A `Signed-off-by` line in the commit message is not enough.

## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
(cherry picked from commit 55d30fb)

## Summary

- docs: remove experimental note from runtime prefetching (#96615)
- docs: proxy event argument (#96435)
- docs: correction to dynamicParams migration (#96624)
- docs: quote the dynamicParams build error in a blockquote (#96633)
- docs: use relative doc links in instant-navigation error pages
(#96672)
- docs: document ! exclusion and src/ prefix for --debug-build-paths
(#96703)
- docs: instant navigation quick start with an adoption prompt (#96663)
- docs (Skills): stop assuming app/ at the root and port 3000 (#96696)
- docs: present each Skill as steps in the AI agents guide (#96751)
- docs: update redirected links to current targets (#96723)
- docs: add authentication with Cache Components guide and iron-session
example (#95802)
- docs: link View Transitions skill on skills.sh and clarify the example
prompt (#96863)
- Add a `turbopackChunking` documentation page for pages router (#96698)
- docs: add `export const dynamic = 'force-static'` to Route Handlers
example on Static Exports (#96964)
- docs: runtime prefetching -> optimizing prefetching (#96934)
- Fix typo in Data Access Layer section (#87202)
- docs: rename repo to repository for consistency (#87849)
- docs(mdx): fix package name in .md handling section (#97131)
- docs: fix Link prefetch grammar and Client Components wording (#97132)
- docs: align Cache Components authentication guide title (#97143)
- docs: create client-side fetching guide (#96341)
- docs: clarify client cache freshness after hydration (#97180)
- docs: server client and directives (#96145)
- Update authentication diagram URL (#97320)
- docs: align SPA guide reducer example with React conventions (#97341)
- docs: app router reference accuracy (#97477)
- docs: mention Valibot as validation library option in forms guides
(#97468)
- docs: warn when catching permanentRedirect (#97496)
- [docs] fix: grammar typos in linking and navigating guide (#95544)
- docs: rename Vercel Edge Config to Global Config in redirecting guide
(#97456)
- docs: document metadata pagination field (#95509)
- docs: outlining and lcp (#96942)
- docs: adjust interactive app guide (#97558)
- docs: generateMetadata values should be serializable with use cache
(#97551)
- Fix stale cross-references in skills/ (#97566)
- Improve Cache Components sync IO migration guidance (#97572)
- docs: Explicit cache output description (#97548)
- docs: document deploymentId build ID override and Pages Router skew in
16.2 (#97645)
- docs: drop stale Route Handlers restriction from `use cache: private`
(docs part of #97349)
- docs: clarify beforeInteractive placement for root layouts (#97643)
- docs: Adapters entry page lists its children pages twice (#97677)
- docs: correct the upper stale bound for App Shell exclusion in
cacheLife (#97653)
- Improve Partial Prefetching adoption checks (#97637)
- docs: fix parallelRouteKey parameter name in
useSelectedLayoutSegment(s) (#97710)
- docs(adapters): document assetsHashes and routing.middlewareMatchers
(#96536)
- docs: note that response headers must be set before calling handle()
in a custom server (#97693)
- Document catchError for the Pages Router (#97748)
- docs: fix typos and correctness issues in App Router docs (#97823)
- docs: param access on use-server (#97865)
- docs: clarify revalidateTag profile expire semantics (#97836)

---------

Co-authored-by: Aurora Scharff <66901228+aurorascharff@users.noreply.github.com>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Co-authored-by: Rich Haines <hello@richardhaines.dev>
Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>
Co-authored-by: Aurora Scharff <aurora.sofie@gmail.com>
Co-authored-by: Sam Poder <sampoder@berkeley.edu>
Co-authored-by: Masashi Kawafuji <masashikawafuji@proton.me>
Co-authored-by: Akseli Palmer <akseli@toddsden.com>
Co-authored-by: Tim Neutkens <tim@timneutkens.nl>
Co-authored-by: Jarren <sanjose.jarren@gmail.com>
Co-authored-by: Marcos Hernanz <96699542+marcoshernanz@users.noreply.github.com>
Co-authored-by: Pavan Shinde <pavann97@gmail.com>
Co-authored-by: Reza Karimzadeh <r.karimzadeh1998@gmail.com>
Co-authored-by: Fabian Hiller <hillerfabian11@gmail.com>
Co-authored-by: David Alexandru Ilie <david@davidilie.com>
Co-authored-by: Sean Beirnes <127370575+seanbeirnes@users.noreply.github.com>
Co-authored-by: Rich Haines <22930449+molebox@users.noreply.github.com>
Co-authored-by: KAM <biukam.w@gmail.com>
Co-authored-by: Jiwon Choi <devjiwonchoi@gmail.com>
Co-authored-by: Jude Gao <jude.gao@vercel.com>
Co-authored-by: Said Nasser <sdnssr001@gmail.com>
Co-authored-by: Eddy (Frontend Engineer) <101346918+leejpsd@users.noreply.github.com>
Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
Co-authored-by: vercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com>
Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>