
from skills520
Opinionated collection of Next.js best practices covering file conventions, RSC boundaries, async patterns, metadata, image/font optimization, error handling an
This skill codifies a set of Next.js engineering best practices and checks to use when writing or reviewing Next.js apps. It covers file and routing conventions, detecting invalid React Server Component patterns, async API patterns, metadata and OG image generation, image/font optimization, error handling patterns, and bundling considerations.
Use this skill during code reviews, pull request checks, architecture discussions, or when onboarding engineers to Next.js 15+ patterns. It is valuable for preventing common pitfalls (hydration errors, invalid server/client boundaries, data waterfalls) and for guiding decisions about runtime selection and bundling.
Useful with code-assistant agents (Copilot/Codeium/GitHub Copilot, Claude Code-like assistants) and any LLM used for code review or automated PR checks.
A well-structured reference skill for Next.js best practices covering 17+ topics from RSC boundaries to self-hosting. No executable scripts — purely a knowledge/lookup skill. Clean frontmatter, good progressive disclosure with lean index SKILL.md pointing to detailed sub-files. Broad audience and practical coverage of common Next.js pain points.
Pure reference/knowledge skill with no executable content. High security score reflects zero attack surface. Quality and architecture scores reflect clean organization and good separation of concerns. Usefulness slightly limited by being reference-only (no automation), but the topic coverage is excellent.