hoangnguyen0403/nextjs-tooling
skills/nextjs/nextjs-tooling/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add hoangnguyen0403/agent-skills-standard nextjs-toolingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 19, 2026, 3:41 AM123.5s3 files scanned
SKILL.md
- name:
- nextjs-tooling
- description:
- 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.
Next.js Tooling
Priority: P2 (MEDIUM)
Standalone Docker Config
See implementation examples
Environment Variable Validation
See implementation examples
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).
References
- CI/CD & Deployment Guide
Related Skills
hoangnguyen0403/common-software-requirements
development
VerifiedTrustedCommunity
Standardize SRS and FRS specifications for technical behavior, interfaces, data contracts, quality constraints, and verification mapping. Use when writing SRS, functional specification, system behavior requirements, API/data contracts, or non-functional thresholds.
503SKILL.mdUpdated May 23, 2026
hoangnguyen0403/common-business-requirements
development
VerifiedTrustedCommunity
Standardize BRD and BRD-lite discovery for business goals, stakeholder impact, current-to-future state, and measurable value outcomes. Use when creating BRD, business case, project justification, ROI narrative, or AS-IS to TO-BE scope.
503SKILL.mdUpdated May 23, 2026
hoangnguyen0403/common-tdd
development
VerifiedTrustedCommunity
Implements a strict Red-Green-Refactor loop to ensure zero production code is written without a prior failing test. Use when: creating new features, fixing bugs, or expanding test coverage.
503SKILL.mdUpdated May 10, 2026
hoangnguyen0403/common-product-requirements
testing
VerifiedTrustedCommunity
Standardize PRD discovery and drafting for product scope, user outcomes, requirement IDs, and acceptance criteria. Use when creating PRD, product requirements, feature specification, or acceptance criteria plan.
503SKILL.mdUpdated May 10, 2026