tauri-impl-design-patterns

Document Tauri 2 IPC and state architecture patterns with decision trees and ADR templates.

4|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/OpenAEC-Foundation/OpenAEC-Workspace-Composer --skill tauri-impl-design-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tauri-impl-design-patterns
Source: https://github.com/OpenAEC-Foundation/OpenAEC-Workspace-Composer/tree/main/.claude/skills/tauri-2/tauri-impl/tauri-impl-design-patterns
Command: npx skills add https://github.com/OpenAEC-Foundation/OpenAEC-Workspace-Composer --skill tauri-impl-design-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Architects and engineering teams need a reliable, documented approach to choosing and wiring IPC and state management for Tauri 2 desktop apps, ensuring consistent frontend-backend boundaries and scalable multi-window behavior.

Core Features & Use Cases

  • IPC decision trees to guide when to use Commands, Events, or Channels.
  • Guidance on where to place state (Rust vs JS) and how to synchronize across windows.
  • Architecture decision records (ADR) templates and reference patterns for common app archetypes.
  • Real-world scenarios including offline-first patterns, progressive disclosure, and robust error handling.

Quick Start

Propose an initial Tauri IPC architecture for a given project by selecting an IPC pattern and a state model.

Frequently Asked Questions about tauri-impl-design-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose between Tauri commands, events, and channels for IPC?

Tauri IPC patterns are selected using decision trees that evaluate whether your frontend-backend boundary requires request-response commands, global event broadcasts, or streaming channels. This provides a documented approach for wiring consistent communication in Tauri 2 desktop apps.

What is the best way to manage state and synchronize it across multiple windows in Tauri 2?

Multi-window synchronization in Tauri 2 is handled by defining state management contracts that dictate whether state lives in Rust or JavaScript. This ensures scalable frontend-backend boundaries and consistent behavior across all application windows.

How do I document and blueprint frontend-backend boundaries for a Tauri app?

You blueprint frontend-backend boundaries for Tauri apps by generating architecture decision records and reference templates. This process documents optimal IPC and state architecture patterns, ensuring consistent boundaries for engineering teams.

Does Tauri 2 architecture support offline-first patterns and streaming data?

Tauri 2 architecture supports offline-first patterns and streaming data through specific IPC reference templates. These templates guide robust error handling and progressive disclosure for real-world desktop application scenarios.

When should I not use global events for Tauri frontend-backend communication?

Global events should be avoided for Tauri frontend-backend communication when dealing with streaming data or strict request-response requirements, as the architecture decision trees recommend using channels or commands instead to ensure robust error handling.