nextjs-expert
Use when implementing nextjs functionality with production-grade patterns and safeguards.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- nextjs-expert
- metadata
- { "hermes": { "tags": [ "codex-agent", "frontend-ui" ], "source": "codex-field-kit/frontend-ui" } }
- description
- Use when implementing nextjs functionality with production-grade patterns and safeguards.
03 SKILL.md 正文
Nextjs Expert
Focus Areas
- Mastery of Next.js server-side rendering (SSR) and static site generation (SSG)
- Implementation of API routes with Next.js
- Integration with popular CMS and headless CMS options
- Configuration of custom document and app in Next.js
- Next.js Image Optimization techniques
- Use of React hooks and context in a Next.js environment
- Managing static and dynamic routing in Next.js
- Employing code splitting and lazy loading for performance
- Authentication and authorization strategies within Next.js
- Leveraging TypeScript for Next.js projects
Approach
- Utilize
getStaticPropsandgetServerSidePropsfor optimal data fetching - Configure Next.js for both CDN and serverless deployments
- Favor static generation with incremental static regeneration where possible
- Use API routes for serverless function scalability
- Integrate third-party services through environment variables
- Optimize build performance with webpack and custom Babel configurations
- Implement custom server logic without ejecting from Next.js
- Apply industry best practices for SEO in Next.js apps
- Utilize Vercel's deployment and preview features for dev workflows
- Structure project for scalability and maintainability
Quality Checklist
- Ensure all pages render correctly with SSR and SSG
- Verify API routes return expected JSON responses
- Review Image component usage for optimized loading
- Check custom client and server configurations align
- Validate TypeScript types across the codebase
- Ensure routing is intuitive and can handle edge cases
- Confirm static assets are correctly cached
- Test performance and loading times meet standards
- Debug and fix any hydration errors
- Conduct thorough accessibility audits
Output
- High-performance Next.js applications tailored to static and dynamic content needs
- APIs seamlessly integrated with external and internal data sources
- Consistent UI/UX with React and Next.js best practices
- Modular, maintainable code following Next.js conventions
- Effective error handling and loading states implemented
- CI/CD pipelines configured for automatic deployments with Vercel
- Documented code with inline comments and README guides
- Optimized media assets using Next.js built-in tools
- Responsive design with server-side responsive data
- Secure Next.js apps with environments for different stages
04 同仓库更多 Skills
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
swarm-planner
[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.
super-swarm-spark
Only to be triggered by explicit super-swarm-spark commands.
role-creator
Create and install Codex custom agent roles in ~/.codex/config.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).
read-github
Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo
planner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.