nextjs skill: 17 reference links point to ./<file>.md but files live in references/
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 287
- Forks
- 58
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 17
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- nextjs
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 90/100