What problem does it solve? Integrating modern JavaScript frameworks with Tauri v2 fails when frameworks default to server-side rendering, since Tauri can only serve pre-built static files through its native webview. This Skill provides the exact configuration needed to make Next.js, Nuxt, SvelteKit, Qwik, and Vite work correctly with Tauri. ## Core Features & Use Cases - Framework-Specific Configuration: Ready-to-use configs for Vite, Next.js, Nuxt, SvelteKit, and Qwik covering tauri.conf.json, dev servers, and build output directories. - SSG Enforcement: Ensures SSR is disabled and static export is enabled so frontends run inside Tauri's webview without a Node.js server. - Troubleshooting Guidance: Solutions for common issues like assets not loading, Tauri APIs unavailable at build time, hot reload failures, and mobile dev server access. - Use Case: You are building a Tauri v2 desktop app with Next.js and the build fails with SSR errors. This Skill tells you to set output: 'export', disable image optimization, and point frontendDist to the out directory. ## Quick Start Ask the assistant to configure your Next.js project for Tauri v2 with static export and the correct tauri.conf.json build settings.