taurilisted

# Tauri Work at the boundary between the web frontend, Rust, and the native application. Use the project's architecture and commands; load only the references needed for the task. ## 1. Identify the project Inspect the Tauri configuration, Cargo manifest and lockfile, builder entry point, and frontend scripts. Account for workspace paths and platform-specific configuration instead of assuming every app has the default layout. Identify the Tauri version, target platforms, existing invoke wrapper, and commands for the relevant development and validation work. Distinguish the host OS from the platforms the application ships on. Done when the affected boundary, target platform, and existing commands are known, or their absence is explicit. ## 2. Choose the work | Task | Read before acting | Completion criterion | | --- | --- | --- | | Commands, state, events, windows, or mobile structure | [Development](best-practices.md) | Changed IPC contracts agree on both sides; platform-specific code remains scoped. | | Plugin integration or permission failures | [Permissions](permissions.md) | Registration, effective capability, target, and operation scope are accounted for. | | Inspecting or reproducing behavior in the application | [Diagnosis](debugging.md) | The intended instance is identified and evidence distinguishes observations from hypotheses. | | Installing, configuring, or troubleshooting the MCP connection | [Agent kit integration](agent-kit.md) | Compatibility and connec