breeze-helper

Explain Breeze Helper architecture and IPC for debugging and extension.

73|23|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/LanternOps/breeze --skill breeze-helper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: breeze-helper
Source: https://github.com/LanternOps/breeze/tree/main/.claude/skills/breeze-helper
Command: npx skills add https://github.com/LanternOps/breeze --skill breeze-helper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a concise, developer-facing reference for Breeze Helper's architecture, IPC surface, and workflow between the React frontend, Rust backend, and Go agent to speed debugging and onboarding.

Core Features & Use Cases

  • Architecture overview: Breeze Helper's components (frontend, backend, and agent integration) and how they interact.
  • IPC mappings and commands: Key Rust↔Frontend interfaces and real-world usage for debugging and extension.
  • Tool approval flow & tray integration: How approvals, config, and data flow support end-to-end conversations and automation.

Quick Start

Launch Breeze Helper Reference in your development environment and review the architecture overview, IPC routes, and configuration notes.

Frequently Asked Questions about breeze-helper

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

FAQPage Schema
How does Tauri IPC work between a React frontend and Rust backend?

Tauri IPC connects the React frontend and Rust backend by exposing mapped command interfaces for real-time data exchange. These documented Rust↔Frontend interfaces define the exact routes and data structures needed to trigger backend logic from the UI.

What is the tool approval flow when integrating a Go agent with a Tauri desktop app?

The tool approval flow routes agent-initiated actions through config-driven checkpoints, requiring explicit frontend or tray-based approval before the Go agent executes commands. This mechanism ensures controlled automation and safe end-to-end conversations.

How do I debug data flow issues between a Go agent, Rust backend, and React UI?

Debug data flow by tracing the IPC commands and approval checkpoints connecting the Go agent, Rust backend, and React UI. Reviewing architecture overviews and IPC mappings isolates communication breakdowns across the helper and frontend components.

Can I extend the IPC commands in my Tauri React and Rust application?

Yes, you can extend Tauri IPC commands by following the documented Rust↔Frontend interface mappings to add new routes. The reference outlines how to correctly wire new backend commands and frontend listeners to ensure proper integration.

Why does my Breeze Helper frontend fail to receive data from the Rust backend?

A frontend fails to receive data when IPC command mappings between Rust and React are mismatched or the tool approval flow blocks transmission. Checking the architecture's data flow and config files identifies the broken listener or blocked agent integration.