Tauri IPC Capabilities Without the Guesswork

Where this fits

You are adding a file-open dialog to a Tauri desktop app. The agent jumps into commands.rs and tauri-client.ts, but never touches the shared contract or capability file; the UI compiles, but the invoke fails at runtime because the command is not allowed in capabilities/default.json. This skill gives the agent the repository-specific IPC workflow: five files in order, typed errors, and least-privilege permissions.

Why agents benefit

• Follows the 5-step IPC flow for every new capability, so no contract, command, client, query hook, or query key is left missing.
• Keeps packages/shared as the single source of truth, which prevents drift between the Rust command signature, Zod schema, and TypeScript caller.
• Uses AppResult instead of Result<_, String> in commands, keeping error handling consistent and serializable across the IPC boundary.
• Wires React Query hooks in the renderer and keeps window.api out of UI code, so data fetching stays testable.
• Makes capability review explicit: new commands must be added to capabilities/default.json, and over-broad filesystem/network scopes are flagged as security findings.

Practical scenarios

Adding a new IPC command to an existing Tauri app

When a feature needs a new invoke call, the agent loads the skill, reads the existing contract files, and adds the Zod schema first. It then implements the command, wires the client, adds a React Query hook, and registers the query key in the same pass.

Refactoring commands.rs to typed errors

A codebase has commands returning Result<_, String> with inconsistent error strings. The skill's command pattern tells the agent to convert them to AppResult and update the renderer call sites to handle the shared error contract.

Auditing capabilities before a release

Before shipping, the agent checks capabilities/default.json against every command referenced in tauri-client.ts. It removes unused permissions and narrows filesystem scopes, applying least privilege without breaking existing flows.

Add it to your agent workflow

Install the skill from the public catalog:

npx skills add saeedkolivand/ai-job-hunter-app --skill tauri-standards

Then ask the agent to apply it:

Load tauri-standards. I need a get_recent_files command for the renderer dashboard. Follow the 5-step IPC flow and keep the fs scope limited to ~/Downloads.

The agent will inspect the existing contracts and implement the capability in the correct order instead of guessing.

Compare before adopting

Before adopting the skill, compare it with the official Tauri IPC docs and any other Tauri agent skills you use. Evaluate maintenance freshness by checking the repo's recent commits and whether the examples match the Tauri version in your project. Also confirm that the shared packages/shared contract workflow matches your monorepo layout; if you use a different directory structure, the five-file order still applies, but the exact paths will need adjustment.

Why it is worth tracking

The skill comes from the ai-job-hunter-app repository with 52 stars and is tied to a real, working Tauri codebase, not an isolated snippet. It is useful to track because it locks in hard-won IPC conventions and security checks that agents often skip, and the explicit step ordering reduces integration defects. For any agent-based Tauri work, it is worth evaluating now, and checking again when your project updates its Tauri version or IPC error model. You can track it at OpenAgentSkill: https://www.openagentskill.com/skills/saeedkolivand-tauri-standards.