tauri
Skill4 starsChanged 21 days agoMITView on GitHub
Tauri 2 development and validation. Use for src-tauri, Rust/frontend IPC, capabilities and plugins, windows, mobile entry points, packaging, or inspecting a running Tauri app with tauri-agent-kit.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- delorenj/skillstheir own version, first seen Nov 7, 2026
- webdevarif/claude-skillstheir own version, first seen Oct 20, 2026
- klauswg/sasuketheir own version, first seen Oct 15, 2026
- G1Joshi/Agent-Skillstheir own version, first seen Oct 13, 2026
- full-stack-skills/tauri-skillstheir own version, first seen Oct 11, 2026
- epicenter-md/epicentertheir own version, first seen Oct 8, 2026
Used with
Projects with it also use tauri-app-autostart, tauri-app-notification and 5 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
pinkpixel-devSkilltauri-app-autostart
Guidance for Tauri v2 autostart setup with platform differences and rollback.
Also in 3 projects that use this
- pinkpixel-devSkill
tauri-app-notification
Guidance for Tauri v2 notification plugin with permission flow and click handling.
Also in 3 projects that use this
- +5 more from pinkpixel-dev
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- epicenter-md/epicenter★ 4.8ksame name
- EpicenterHQ/epicenter★ 4.8ksame name
- diodeme/Gold-Band★ 164same name
- full-stack-skills/tauri-skills★ 20same name
- delorenj/skills★ 17same name
- klauswg/sasuke★ 17same name
- G1Joshi/Agent-Skills★ 15same name
- lindoelio/agent-skills★ 3same name
- musaJawad004/heron★ 1same name
- pinkpixel-dev/tauri-skills★ 1same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository39 other files it gives its agents.
- AGENTS.mdAGENTS.md
- authoringSkill
- chrome-devtoolsSkill
- gamificationSkill
- imagegenSkill
- improve-architectureSkill
- instructionsSkill
- monorepoSkill
- reverse-engineerSkill
- runbookSkill
- security-reviewSkill
- setup-harnessSkill
- skillsSkill
- unslopSkill
- video-reportSkill
- youtube-transcriptSkill
- code-reviewSkill
- debugSkill
- interviewSkill
- prototypeSkill
- researchSkill
- workSkill
- adsenseSkill
- astryxSkill
- cloudflare-cliSkill
- dokploy-best-practicesSkill
- extract-themeSkill
- nextjsSkill
- payload-cmsSkill
- shadersSkill
- swrSkill
- tanstack-querySkill
- tanstack-routerSkill
- tanstack-startSkill
- tanstack-storeSkill
- vite-plusSkill
- web-assets-optimizationSkill
- web-extensionSkill
- zodSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use the project's architecture and commands.
- Distinctive: line 31
When it is missing or incomplete and the project can use it, propose the integration once per session as described in Propose the …
- Distinctive: line 55
Prefer tauri-agent-kit for supported Windows development sessions.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Tauri
Work at the boundary between the web frontend, Rust, and the native application. Use the project's architecture and commands; load only the references needed for the task.
1. Identify the project
Inspect the Tauri configuration, Cargo manifest and lockfile, builder entry point, and frontend scripts. Account for workspace paths and platform-specific configuration instead of assuming every app has the default layout.
Identify the Tauri version, target platforms, IPC bindings, their generation process, and the project's validation commands. Distinguish the host OS from the platforms the application ships on.
For any Rust/TypeScript IPC work, apply the mandatory Tauri Specta contract in Commands and IPC. Before changing an exposed operation, its permissions, a remote origin, or the CSP, read Permissions.
Detect whether the project integrates tauri-agent-kit. When it is missing or incomplete and the project can use it, propose the integration once per session as described in Propose the integration, then continue the requested work while awaiting the answer.
Done when the affected boundary, target platform, existing commands, and agent-kit integration status are known, or their absence is explicit.
2. Choose the work
| Task | Read before acting | Completion criterion |
| Commands, state, events, windows, or mobile structure | Development | Changed IPC contracts agree on both sides; platform-specific code remains scoped. |
| Plugin integration or permission failures | Permissions | Registration, effective capability, target, and operation scope are accounted for. |
| Inspecting or reproducing behavior in the application | Diagnosis | The intended instance is identified and evidence distinguishes observations from hypotheses. |
| Installing, configuring, or troubleshooting the MCP connection | Agent kit integration | Compatibility and connection are verified, or the missing prerequisite is reported. |
| Validating a change, including bundles | Testing | Relevant layers have results; skipped layers have reasons. |
Tasks may cross boundaries: a plugin fix needs both permissions and validation. For an authorized v1 migration, consult the official migration guide and the development and permissions references. Account for changed imports, window APIs, and plugin permissions within the requested migration scope.
Prefer tauri-agent-kit for supported Windows development sessions. Its availability is separate from Tauri's desktop/mobile support. Until an integration is approved and connected, continue with existing evidence; installing the kit or upgrading Tauri happens only after the user approves the proposal.
3. Verify and report
For implementation work, apply Testing to the changed boundary. For runtime sessions, complete Diagnosis cleanup.
Report the change or finding, checks performed, evidence source and target, and remaining uncertainty. A browser-only result, successful compilation, or dispatched UI action alone is not proof that the native application works.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.