Guide renderer-to-Rust integration for Tauri 2 apps using Specta typed bindings.
npx skills add https://github.com/jonaseck2/slaktforskning --skill tauri-bridge
Please help me install this Agent Skill. Skill: tauri-bridge Source: https://github.com/jonaseck2/slaktforskning/tree/main/.claude/skills/tauri-bridge Command: npx skills add https://github.com/jonaseck2/slaktforskning --skill tauri-bridge
This Skill prevents Tauri renderer ↔ Rust integration mistakes by guiding how to correctly add, type, and wire new API bindings so features work reliably across file I/O, dialogs, media, multi-window orchestration, and SQLite access.
#[tauri::command] and #[specta::specta], deriving specta::Type for all involved types, and registering commands so bindings.ts is regenerated.api.* polyfills that call typed commands.*, handle Specta Result<T, String> envelopes safely, and follow the success/error object convention.Update src/renderer/tauri-window-api.ts when the change can be expressed as pure TypeScript over the renderer DB shim, otherwise add a Rust #[tauri::command] with #[specta::specta] in src-tauri/ and regenerate src/renderer/bindings.ts before wiring a matching renderer polyfill.
High-intent search queries and answers about installing and using this skill.
To add a Rust command in Tauri 2, annotate your function with #[tauri::command] and #[specta::specta], register it in collect_commands!, then regenerate bindings.ts to wire the renderer polyfill.
Use a TypeScript polyfill in tauri-window-api.ts when a task operates purely over the renderer database shim, and use a native Rust command when requiring filesystem, dialogs, media, or multi-window orchestration.
Specta typed bindings act as the source of truth for Tauri IPC by deriving specta::Type for involved Rust structs, generating a bindings.ts file, and enforcing renderer invoke and error-handling conventions safely.
Handle Specta Result envelopes in a Tauri renderer by implementing api polyfills that call typed commands, safely unwrapping the Result<T, String> object, and following the established success or error object convention.
The JsonValueWire workaround is a provided type derivation method used when deriving specta types for Tauri commands, ensuring complex JSON values are correctly typed across the Rust to renderer bridge.
Yes, this Tauri bridge approach supports multi-window orchestration and SQLite access by selecting the correct bridge mechanism for each feature and defining typed renderer polyfills for secondary databases.
OpenAEC-FoundationGuide Tauri 2 project structure with backend, webview, and IPC boundaries.
OpenAEC-FoundationCoordinate Tauri windows and events across Rust and JavaScript.
vobaseIntegrate Better Auth authentication into TypeScript applications with SQLite, Prisma, or Drizzle.
nikrichCall Rust backend functions from Tauri v2 frontends via typed IPC commands.