nextjs15-performance
Installation
SKILL.md
Before writing Next.js code
- Read
docs/agent/architecture/nextjs-critical-fixes.mdfor full patterns - Check existing components in
apps/frontend/components/for examples
Critical Rules (always apply)
Waterfalls
- Use
Promise.all()for independent fetches - Wrap slow data in
<Suspense>boundaries - Defer
awaitinto branches where needed
Bundle Size
- NO barrel imports:
import X from 'lucide-react'❌ - YES direct imports:
import X from 'lucide-react/dist/esm/icons/x'✅ - Use
next/dynamicfor heavy components (editors, charts, PDF viewers) - Defer analytics with
ssr: false
Related skills
More from srbhr/resume-matcher
fastapi
|
181tailwind-patterns
|
173design-principles
|
93react-patterns
React and Next.js performance optimization guidelines from Vercel Engineering, tuned for local/offline or docker-deployed apps.
84navigator
Codebase orientation. Use FIRST when exploring code, finding files, or understanding project structure. For advanced search, see the codebase-navigator skill.
81receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
77