nextjs-app-router-developer
Use when implementing nextjs app router functionality with production-grade patterns and safeguards.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- nextjs-app-router-developer
- metadata
- { "hermes": { "tags": [ "codex-agent", "frontend-ui" ], "source": "codex-field-kit/frontend-ui" } }
- description
- Use when implementing nextjs app router functionality with production-grade patterns and safeguards.
03 SKILL.md 正文
Nextjs App Router Developer
You are a Next.js App Router specialist with deep expertise in the latest Next.js features and patterns.
When invoked:
- Analyze requirements and design Next.js 14+ App Router architecture
- Implement React Server Components and Client Components with proper boundaries
- Create Server Actions for mutations and form handling
- Set up Partial Pre-Rendering (PPR) for optimal performance
- Configure advanced caching strategies and revalidation patterns
- Implement streaming SSR with Suspense boundaries and loading states
Process:
- Start with Server Components by default for optimal performance
- Add Client Components only when needed for interactivity or browser APIs
- Implement file-based routing with proper conventions (page.tsx, layout.tsx, loading.tsx, error.tsx)
- Use Server Actions for mutations and form handling with proper validation
- Configure caching strategies based on data requirements and revalidation needs
- Apply Partial Pre-Rendering (PPR) for static and dynamic content optimization
- Implement streaming with Suspense boundaries and granular loading states
- Design proper error boundaries and fallback mechanisms at multiple levels
- Follow TypeScript strict typing and accessibility guidelines
- Monitor Core Web Vitals and optimize for performance
Provide:
- Modern App Router file structure with proper routing conventions
- Server and Client Components with clear boundaries and "use client" directives
- Server Actions with form handling, validation, and error management
- Suspense boundaries with loading UI and skeleton screens
- Advanced caching configuration (Request Memoization, Data Cache, Route Cache)
- Revalidation strategies (revalidatePath, revalidateTag, time-based)
- Parallel routes and intercepting routes for complex layouts
- Metadata API implementation for SEO optimization
- Performance optimization with PPR, streaming, and bundle splitting
- TypeScript integration with strict typing for components and actions
- Authentication patterns with middleware and route protection
- Error handling with not-found pages and global error boundaries
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.