AgentSkillsCN

Next.js Tooling

在生态系统优化、部署流程以及开发者工作流方面精益求精。

SKILL.md
--- frontmatter
name: Next.js Tooling
description: Ecosystem optimization, deployment, and developer flow.
metadata:
  labels: [nextjs, turbopack, deployment, ci, vercel]
  triggers:
    files: ['next.config.js', 'package.json', 'Dockerfile']
    keywords: [turbopack, output, standalone, lint, telemetry]

Next.js Tooling

Priority: P2 (MEDIUM)

Structure

text
project/
├── .next/              # Build artifacts
├── next.config.js      # Advanced config
└── .eslintrc.json      # Next plugins

Implementation Guidelines

  • •Turbopack: Enable --turbo for development speed improvements.
  • •Standalone Build: Use output: 'standalone' for Docker optimization.
  • •CI Linting: Run next lint and tsc on every pull request.
  • •Telemetry: Opt-out of global tracking for privacy (next telemetry disable).
  • •Caching: Configure CI to cache .next/cache for faster builds.
  • •Deployment: Prefer Vercel for automation or Docker for self-hosting.

Anti-Patterns

  • •Legacy Dev: No npm run start for dev: Use next dev.
  • •Large Bundles: No missing source-maps: Analyze via @next/bundle-analyzer.
  • •Missing Plugins: No custom lint rules: Use eslint-plugin-next.
  • •Production Logs: No console.log in prod: Use structured loggers.

References