Nextjs tooling
Skills for my agentic development workflow.
npx -y skills add FilippoDeSilva/skills --skill nextjs-toolingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Configure Next.js build tooling, deployment, and developer workflow. Use when setting up Turbopack, standalone Docker output, bundle analysis, CI caching, environment variable validation, or ESLint integration for Next.js projects.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.8 KB, as published. Nobody here has run it
Next.js Tooling
Priority: P2 (MEDIUM)
Standalone Docker Config
Environment Variable Validation
Implementation Guidelines
- Build: Use Turbopack (
next dev --turbo) for faster incremental builds; Webpack for legacy. - Linting: Mandate
next lint(eslint-plugin-next) andtscin CI/CD. - Bundle Analysis: Inspect with
@next/bundle-analyzer. Remove unused dependencies. - Telemetry: Opt-out via
next telemetry disableif privacy required. - Environment: Server-only vars vs
NEXT_PUBLIC_*. Validate with Zod at runtime. - CI/CD: Cache
.next/cachein CI for 50%+ faster builds.
Anti-Patterns
- No
npm run startfor dev: Usenext dev(ornext dev --turbo). - No uninspected bundle growth: Analyze with
@next/bundle-analyzerbefore shipping. - No custom ESLint rules over plugin: Use
eslint-plugin-nextfor Next.js-aware linting. - No
console.login production: Use structured loggers (Pino, Winston).