Tauri Architecture Patterns

Design from ownership and runtime boundaries. Inspect the target repository before recommending structure or dependencies.

Establish the Baseline

1. Read Rust and frontend manifests, Tauri configuration, capabilities, and application setup.
2. Locate commands, events, managed state, background tasks, generated types, Query configuration, stores, Context providers, and persistence adapters.
3. Identify which values are authoritative, cached, derived, transient, or window-local.
4. Preserve sound repository conventions. Change a pattern only when its ownership, security, lifecycle, or testability cost is concrete.

Do not assume a src-tauri layout, one Rust crate, tauri-specta, Zustand, TanStack Query, shadcn/ui, or React Compiler is present.