What problem does it solve? Debugging Tauri v2 applications is difficult because the app spans a Rust backend and a WebView frontend, and standard IDE debuggers bypass the Tauri CLI, breaking dev server startup and breakpoint attachment. This Skill provides working configurations and workflows for each major editor. ## Core Features & Use Cases - IDE Debug Configurations: Ready-to-use launch.json, tasks.json, and Run Configuration setups for VS Code (LLDB/cppvsdbg), RustRover/IntelliJ, and Neovim (nvim-dap + codelldb). - WebView and Console Debugging: Instructions for opening WebView DevTools programmatically, enabling Rust backtraces, and using conditional compilation (cfg(dev), debug_assertions) to separate debug from production code. - CrabNebula DevTools Integration: Setup of tauri-plugin-devtools for real-time log inspection, IPC command timing, and event analysis. - Use Case: Your breakpoints in Rust code are never hit when running tauri dev from VS Code. This Skill explains that you must build with --no-default-features and configure a preLaunchTask to start the frontend dev server before the debugger attaches. ## Quick Start Ask the assistant to set up a VS Code debug configuration for your Tauri v2 app so breakpoints in Rust code are hit during development.