nextjs15-performance
提供Next.js 15性能优化指南和最佳实践，确保代码质量和应用效率，参考现有组件范例。
npx skills add srbhr/resume-matcher --skill nextjs15-performanceBefore / After 效果对比
1 组1在没有 `nextjs15-performance` 技能指导时，Next.js 15 应用可能存在性能瓶颈，例如数据瀑布式请求（waterfalls）、过大的打包体积或不当的 Suspense 使用，导致页面加载缓慢和用户体验不佳。1使用 `nextjs15-performance` 技能后，可以遵循关键规则对 Next.js 15 应用进行性能优化。技能会指导开发者使用 `Promise.all()` 处理独立的数据请求、将慢速数据包裹在 `<Suspense>` 边界中、延迟 `await` 到需要的分支，并避免 barrel imports 以减小打包体积，从而显著提升应用性能和用户体验。description SKILL.md
nextjs15-performance
Before writing Next.js code Read docs/agent/architecture/nextjs-critical-fixes.md for 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 boundaries Defer await into 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/dynamic for heavy components (editors, charts, PDF viewers) Defer analytics with ssr: false Server Actions ALWAYS check auth INSIDE the action, not just middleware Verify resource ownership before mutations Production Build Users run npm run build && npm run start, NOT npm run dev Docker must use standalone output, not dev mode Quick Check Before PR [ ] No sequential awaits for independent data [ ] Icons imported directly [ ] Heavy components use next/dynamic [ ] Server Actions have auth inside [ ] Suspense around slow fetches Weekly Installs190Repositorysrbhr/resume-matcherGitHub Stars26.3KFirst SeenJan 22, 2026Security AuditsGen Agent Trust HubPassSocketPassSnykPassInstalled onopencode166codex160gemini-cli157github-copilot150cursor136claude-code135
forum用户评价 (0)
发表评价
暂无评价，来写第一条吧
统计数据
用户评分
为此 Skill 评分