What problem does it solve? Developers migrating to or working with Turbopack in Next.js often struggle with config migration from webpack, missing loader equivalents, CSS ordering differences, and build failures that are hard to diagnose without bundler-specific knowledge. ## Core Features & Use Cases - Configuration Guidance: Set up top-level turbopack config in Next.js 16, including resolveAlias, resolveExtensions, and custom rules. - Webpack Migration: Map common webpack loaders (sass-loader, svgr, raw-loader) to Turbopack equivalents or fall back to webpack when needed. - Build Diagnostics: Troubleshoot production build failures, oversized bundles, HMR issues, and profile performance with tracing. - Use Case: You just upgraded to Next.js 16 and your experimental.turbopack config stopped working. Use this Skill to migrate to the new top-level config syntax and fix the resulting build errors. ## Quick Start Ask the AI to migrate your next.config webpack customizations to the Turbopack top-level config format in Next.js 16.