Nextjs tooling

Skill ComeOnOliver/skillshub/skills/HoangNguyen0403/agent-skills-standard/nextjs-tooling

Ecosystem optimization, deployment, and developer flow. Use when configuring Next.js build optimization, deployment settings, or developer tooling. (triggers: next.config.js, package.json, Dockerfile, turbopack, output, standalone, lint, telemetry)From its SKILL.md

Install

npx -y skills add ComeOnOliver/skillshub --skill nextjs-tooling

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

1.8 KB, 421 tokens by cl100k_base, as published. Nobody here has run it

Next.js Tooling

Priority: P2 (MEDIUM)

Structure

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

Implementation Guidelines

Build Architecture: Use Turbopack (modern) or Webpack (legacy). Enable --turbo for faster incremental development.
Minification: Ensure output: 'standalone' is set in next.config.js for optimized Docker deployments. Use ProGuard / Uglify equivalents for asset shrinking.
Linting: Mandate next lint (Next.js ESLint plugin) and tsc (typecheck) in CI/CD pipelines.
Asset Optimization: Inspect size with @next/bundle-analyzer. Optimize images via next/image and remove unused dependencies.
Telemetry: Opt-out via next telemetry disable if privacy is required.
Environment: Use .env management in Next.js (Server only vs NEXT_PUBLIC_*). Validate schemas with Zod at runtime.
CI/CD: Cache the .next/cache folder in CI for 50%+ faster build times.

Anti-Patterns

No npm run start for dev: Use next dev (or next dev --turbo).
No uninspected bundle growth: Analyze with @next/bundle-analyzer before shipping.
No custom ESLint rules over plugin: Use eslint-plugin-next for Next.js-aware linting.
No console.log in production: Use structured loggers (Pino, Winston).

References

CI/CD & Deployment Guide

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.