Clean

next-best-practices

Name: next-best-practices
Author: vercel-labs

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

engineering›web-development

Publisher vercel-labs

Sourceskills.sh

TypeDomain expertise

Popularity89,987

UpdatedJun 1, 2026, 05:51 AM

Manifest Score89

Lineage Score89

Safety Score100

Ecosystem Rank2252

Registryskills.sh/vercel-labs/next-skills/next-best-practices

Publisher vercel-labs

Sourceskills.sh

TypeDomain expertise

Popularity89,987

UpdatedJun 1, 2026, 05:51 AM

Manifest Score89

Lineage Score89

Safety Score100

Ecosystem Rank2252

Registryskills.sh/vercel-labs/next-skills/next-best-practices

Analysis Graphs

Primary skill entry point

Configuration file references

Version control operations

Repository status checks

Primary skill entry point

External repository references

Miscellaneous safe nodes

Security Findings

No tagged releases

Repo ships no git tags and no GitHub releases — consumers cannot pin to stable, reviewable versions

No license file

No license file at the repo root and GitHub's licenseInfo is empty — code's legal status is unclear

Versions

89
Clean
Scanned Jun 1, 2026, 05:51 AM
Clean
Scanned Apr 28, 2026, 04:52 PM
Clean
Scanned Apr 7, 2026, 02:00 PM