What problem does it solve? Tauri v2 applications ship without a Content Security Policy by default, leaving the WebView exposed to XSS attacks and unauthorized resource loading. This Skill guides developers through writing correct, restrictive CSP configurations in tauri.conf.json. ## Core Features & Use Cases - Directive-by-Directive Guidance: Explains default-src, script-src, style-src, connect-src, img-src, font-src, and other directives with Tauri-specific values like ipc:, asset:, and customprotocol:. - Framework-Specific Templates: Provides ready configurations for React/Vue/Svelte apps and Rust/WASM frameworks (Leptos, Yew, Dioxus) requiring 'wasm-unsafe-eval'. - Troubleshooting Coverage: Diagnoses common CSP violations such as blocked scripts, broken WebAssembly, non-working inline styles, and IPC connection failures. - Use Case: A developer hardening a Tauri desktop app before release uses this Skill to write a restrictive CSP, enable freezePrototype, and resolve console CSP violation errors. ## Quick Start Ask the assistant to generate a secure CSP configuration for your Tauri v2 app in tauri.conf.json.