nextjs skill: 17 reference links point to ./<file>.md but files live in references/

Open Beginner friendly
#182 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
90/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
nextjs
Domain
documentation

Research direction

Start by comparing the 17 links in skills/nextjs/SKILL.md and skills/nextjs/upstream/SKILL.md with the files under skills/nextjs/references/. Update the affected links to use the references/ path, then verify that every listed target resolves and that no affected link still points directly from the skill directory.

Written by the indexing model from the issue text.

Description

In skills/nextjs/SKILL.md (plugin v0.49.1), the "See x" links resolve relative to the skill directory, but the files are shipped under skills/nextjs/references/. The same happens in skills/nextjs/upstream/SKILL.md.

Example (line 294):

See [file-conventions.md](./file-conventions.md) for:

skills/nextjs/file-conventions.md does not exist; skills/nextjs/references/file-conventions.md does.

Affected links (17): file-conventions, rsc-boundaries, async-patterns, runtime-selection, directives, functions, error-handling, data-patterns, route-handlers, metadata, image, font, bundling, scripts, hydration-error, suspense-boundaries, parallel-routes, self-hosting, debug-tricks.

Impact: an agent following the link gets a missing file and skips the detailed guidance.

Suggested fix: change ./<name>.md to ./references/<name>.md in both SKILL.md files.

Dominant language
TypeScript
Stars
287
Forks
58
Avg merge
1d 24m
Merged PRs (30d)
18

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from vercel/vercel-plugin

All issues in vercel/vercel-plugin

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.