What problem does it solve? Setting up a Next.js 16 project for fully static export involves many failure points: missing generateStaticParams, incompatible server-only APIs, async params migration, and misconfigured next.config.ts. This Skill provides a verified procedure to scaffold, configure, and validate static Next.js sites so pnpm build reliably produces correct output in out/. ## Core Features & Use Cases - Project Scaffolding: Create a new Next.js 16 project with TypeScript, Tailwind, ESLint, App Router, and pnpm using the correct flags. - Static Export Configuration: Set output: 'export', trailingSlash, and images.unoptimized in next.config.ts, including next-intl plugin wrapping. - Dynamic Route Handling: Implement generateStaticParams for locale, slug, and catch-all segments with Next.js 16 async params conventions. - Build Debugging: Diagnose common failures like missing generateStaticParams, ISR incompatibility, and server-only API usage. - Use Case: You need a marketing site deployed to static hosting. Use this Skill to scaffold the project, configure static export with localized routes, and verify the out/ directory contains all expected HTML files. ## Quick Start Scaffold a new Next.js 16 project configured for static export with TypeScript and Tailwind, then verify the build output in the out directory.