nextjs-turbopack
Next.js 16+ and Turbopack — incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack.
Install
git clone https://github.com/affaan-m/ECC /tmp/ECC && ln -s /tmp/ECC/skills/nextjs-turbopack ~/.claude/skills/nextjs-turbopack
From README
Next.js and Turbopack Next.js 16+ uses Turbopack by default for local development: an incremental bundler written in Rust that significantly speeds up dev startup and hot updates. When to Use Turbopack (default dev): Use for day-to-day development. Faster cold start and HMR, especially in large apps. Webpack (legacy dev): Use only if you hit a Turbopack bug or rely on a webpack-only plugin in dev. Disable with --webpack (or --no-turbopack depending on your Next.js version; check the docs for your release). Production: Production build behavior (next build) may use Turbopack or webpack depending on Next.js version; check the official Next.js docs for your version. Use when: developing or debugging Next.js 16+ apps, diagnosing slow dev startup or HMR, or optimizing production bundles. How It Works Turbopack: Incremental bundler for Next.js dev. Uses file-system caching so restarts are much faster (e.g. 5–14x on large projects).
More from this repo
api-design
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning,...
article-writing
Used to write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive...
brand-voice
Used to build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then...
