What problem does it solve? Developers building Tauri desktop applications often struggle to understand how the Rust Core process and WebView processes interact, leading to insecure designs, misplaced business logic, and confusion around multiwindow communication and IPC. ## Core Features & Use Cases - Process Architecture Reference: Details the responsibilities of the Core process (window management, IPC routing, global state, OS abstractions) versus WebView processes (UI rendering only). - IPC and Multiwindow Patterns: Provides Rust and JavaScript code examples for invoke/listen communication, cross-window events, and window-specific messaging. - Security Guidance: Explains process isolation, the principle of least privilege, and capability-based permission configuration per window. - Use Case: When designing a Tauri app with a main window and a settings window, use this Skill to decide which commands belong in the Core process and how to scope capabilities so the settings window cannot access the file system. ## Quick Start Explain how the Tauri Core process and WebView processes communicate and show me how to securely share state between multiple windows.