What problem does it solve? Tauri applications expose backend APIs to the frontend, and without proper capability configuration every window can access every command, creating security risks. This Skill guides you through defining granular capability files so each window only gets the permissions it actually needs. ## Core Features & Use Cases - Capability File Authoring: Create JSON or TOML capability files in src-tauri/capabilities with identifiers, window targets, permissions, and platform constraints. - Per-Window Security Boundaries: Assign different permission sets to main, settings, and preview windows using labels and wildcard patterns. - Platform-Specific Configuration: Target desktop (linux, macOS, windows) or mobile (iOS, android) platforms with separate capability variants, plus remote URL access rules. - Use Case: You are building a multi-window Tauri 2 desktop app and need the settings window to have read-only file access while the main window retains full fs, shell, and dialog permissions. ## Quick Start Ask the AI to create a Tauri capability file that grants the main window default core and filesystem permissions while restricting the settings window to read-only access.