What problem does it solve? Tauri applications can ship with unnecessarily large binaries when default Cargo release settings are used, and developers often lack a clear reference for which profile flags, LTO modes, and Tauri build options actually reduce bundle size. ## Core Features & Use Cases - Cargo Profile Optimization: Provides ready-to-use [profile.release] settings including codegen-units = 1, lto = true, opt-level = "s", panic = "abort", and strip = true, with explanations of each option's trade-offs. - Tauri Build Configuration: Covers removeUnusedCommands in tauri.conf.json (Tauri 2.4+) and guidance on enabling only the Tauri features your app actually needs. - Nightly Toolchain Options: Documents extra optimizations like trim-paths and build-override profiles for teams using the nightly Rust toolchain. - Use Case: Before shipping a production release of a Tauri 2 desktop app, apply the complete example Cargo.toml and tauri.conf.json configurations, then verify the resulting AppImage, MSI, or .app bundle size with the provided check commands. ## Quick Start Ask the assistant to optimize your Tauri app's release binary size by updating src-tauri/Cargo.toml and tauri.conf.json with the recommended profile and build settings.