tauri-stinger skill
scriptsEnables engineering for Tauri 2 desktop and mobile applications, including migration, IPC design, security configuration, and distribution.
- GitHub stars
- 95
- Files
- 42
- Last commit
- Oct 18, 2026
- License
- AGPL-3.0-or-later
- Allowed tools
- —
What does the tauri-stinger skill do?
tauri-stinger enables engineering for Tauri 2 desktop and mobile applications, including migration, IPC design, security configuration, and distribution.
Summary generated from the skill's SKILL.md.
About the tauri-stinger skill
Engineering Tauri 2 desktop and mobile applications is the primary focus of this skill. It assists developers in managing the entire application lifecycle, from initial creation and version upgrades to complex migrations from Tauri 1. The tool provides specific guidance for designing Rust commands, frontend invoke calls, and managing application state through options like Store, SQL, or Stronghold.
When an agent loads this skill, it can perform deep inspections of existing projects using a Python-based inspector script to generate a read-only JSON inventory. It is particularly useful for configuring security boundaries such as capabilities, permissions, and CSP, as well as integrating AI runtimes via hosted providers, local sidecars, or native plugins. Developers can rely on it to qualify native behaviors, build installers, and manage the signing and distribution process for macOS, Windows, and Linux platforms.
What an agent can do with it
- 1Migrate Tauri 1 to 2An AI client can guide a developer through the process of upgrading an older project to the latest Tauri version.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the tauri-stinger skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the tauri-stinger skill in Plugin
/plugin marketplace add legioncodeinc/vibe-coding-tools /plugin install backend-and-desktop-tools@wasp-nest
Install the tauri-stinger skill in Claude Code
~/.claude/skills/tauri-stinger/SKILL.md
$ npx degit legioncodeinc/vibe-coding-tools/plugins/backend-and-desktop-tools/skills/tauri-stinger ~/.claude/skills/tauri-stingerInstall the tauri-stinger skill in Claude Code (project)
.claude/skills/tauri-stinger/SKILL.md
$ npx degit legioncodeinc/vibe-coding-tools/plugins/backend-and-desktop-tools/skills/tauri-stinger .claude/skills/tauri-stingerInstall the tauri-stinger skill in Codex
~/.agents/skills/tauri-stinger/SKILL.md
$ npx degit legioncodeinc/vibe-coding-tools/plugins/backend-and-desktop-tools/skills/tauri-stinger ~/.agents/skills/tauri-stingerInstall the tauri-stinger skill in Gemini CLI
~/.gemini/skills/tauri-stinger/SKILL.md
$ npx degit legioncodeinc/vibe-coding-tools/plugins/backend-and-desktop-tools/skills/tauri-stinger ~/.gemini/skills/tauri-stingerInstall the tauri-stinger skill in Claude.ai
npx degit legioncodeinc/vibe-coding-tools/plugins/backend-and-desktop-tools/skills/tauri-stinger tauri-stinger && zip -r tauri-stinger.zip tauri-stinger # claude.ai → Customize → Skills → + → Create skill → Upload a skill → tauri-stinger.zip
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A skill needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablelegioncodeinc/vibe-coding-tools/plugins/backend-and-desktop-tools/skills/tauri-stinger is public and reachablegithub.com/legioncodeinc/vibe-coding-tools/tree/HEAD/plugins ↗Pass
- Open source license (OSI)AGPL-3.0-or-later is not OSI-approvedspdx.org/licenses/AGPL-3.0-or-later.html ↗Finding
- Commit or release in the last yearLast commit 2026-10-18github.com/legioncodeinc/vibe-coding-tools/commits ↗Pass
- No download-and-run or credential theft in scripts2 scripts read; no download-and-run, remote eval, base64 execution or credential uploadPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/legioncodeinc/vibe-coding-tools/blob/HEAD/plugins ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/legioncodeinc/vibe-coding-tools/blob/HEAD/plugins ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 103 linesgithub.com/legioncodeinc/vibe-coding-tools/blob/HEAD/plugins ↗Pass
SKILL.md
View on GitHubTauri Stinger
Start with README.md for the workflow map and detailed references.
Purpose
Equip tauri-wasp-drone to inspect, migrate, implement, secure, test, and distribute Tauri 2 desktop and mobile applications. It includes a dated six-month update sweep, compact primary-source captures, supplemental living baseline documentation, and derived patterns for hosted and local AI applications.
When to use
- Creating, upgrading, or debugging a Tauri 2 desktop or mobile application
- Migrating a Tauri 1 project to Tauri 2
- Aligning
tauri,@tauri-apps/api, CLI, plugin, runtime, Wry, or Tao versions - Designing Rust commands, frontend
invoke, events, Channels, managed state, or cancellation - Configuring capabilities, permissions, scopes, CSP, remote origins, or sidecar access
- Building a hosted-provider, local-sidecar, native-runtime, or mobile-plugin AI feature
- Qualifying local import, export, app-data cleanup or uninstall without losing user documents
- Choosing Store, SQL, Stronghold, or managed state for application data
- Testing native behavior, building installers, signing, updating, or distributing a Tauri application
- Refreshing current Tauri 2 release and security notes from primary sources
When not to use
- General Rust language, Cargo, async, unsafe, or library architecture unrelated to Tauri; use rust-stinger.
- Frontend-framework component design or reactivity; use the relevant framework Stinger such as svelte-stinger or react-stinger.
- Formal security audit of the resulting implementation; use security-stinger after Tauri implementation work.
- CI platform architecture or release automation beyond Tauri-specific integration; use ci-release-stinger or devops-stinger.
- Dependency vulnerability triage, SBOMs, or update-bot policy; use dependency-audit-stinger.
Procedure
- Establish authority and scope. Read guides/00-authority-and-scope.md. Keep dated Tauri facts separate from derived AI designs.
- Inspect before editing. Follow guides/01-inspect-and-align.md, resolve
scripts/inspect-tauri-project.pyrelative to this loadedSKILL.md, and runpython <resolved-script-path> <project-root> --prettyfor a read-only JSON inventory. - Refresh mutable versions. Read references/CURRENT-TAURI-2.md as a dated snapshot, then use guides/09-refresh-current-tauri.md before making present-tense version claims.
- Migrate deliberately. For Tauri 1, execute guides/02-migrate-v1-to-v2.md in bounded slices and manually review generated capabilities.
- Design IPC and state. Use guides/03-design-ipc-and-state.md for typed commands, structured errors, ordered Channels, event cleanup, managed state, timeouts, and cancellation.
- Constrain authority and secrets. Apply guides/04-secure-capabilities-and-secrets.md. Treat custom scope enforcement as authorization code and keep publisher-owned secrets outside the client.
- Choose the AI topology. Use guides/05-integrate-ai-runtimes.md and label the hosted-provider, desktop-sidecar, native-runtime, or mobile-plugin result as a derived application design.
- Classify persistence. Follow guides/06-persist-ai-state.md to separate preferences, structured records, user-owned secrets, and ephemeral runtime handles.
- Verify real behavior. Follow guides/07-test-desktop-and-mobile.md. Distinguish mocked, browser-only, native, packaged, and physical-device evidence.
- Build and distribute. For platform release qualification, use macOS, Windows, or Linux with the evidence record. Complete guides/08-build-sign-update-distribute.md and references/RELEASE-CHECKLIST.md, then enter the Ship Gate.
Desktop capability qualification update
For sidecar credentials use guide 13; for local schema upgrades and recoverable data use guide 14; for updater key/version/data transitions use guide 15; for tray, shortcuts and notifications use guide 16; for real app acceptance beyond browser tests use guide 17. Read the 2026-10-07 evidence digest, complete the record, and distinguish synthetic decisions and the temporary SQLite exercise from native app proof.
References map
- references/REFERENCE.md, load for the full project, version, IPC, platform, escalation, and red-flag decision tables.
- references/CURRENT-TAURI-2.md, load before an update, migration, security-floor, or "latest version" question; every value is dated 2026-09-03.
- references/IPC-SECURITY-REFERENCE.md, load when designing commands, Channels, capabilities, scopes, CSP, sidecars, or secret boundaries.
- references/AI-ARCHITECTURE-REFERENCE.md, load when choosing hosted, local, native, or mobile AI architecture and stream contracts.
- references/RELEASE-CHECKLIST.md, load before packaging, signing, updating, publishing, or claiming release readiness.
- references/research/distilled-tauri-2.md, load when a domain claim needs verification or a conflict needs resolution.
- Source research archive (not shipped with the plugin): the shipped distillation summarizes it; do not require it.
examples/, load the one example matching the task: typed AI Channel, hosted command boundary, local sidecar, least-privilege capability, v1 migration, or signed updater flow.templates/, copy the relevant inspection, AI decision, capability review, upgrade plan, or release evidence template into the consumer repository's planning or report location.scripts/inspect-tauri-project.py, run for deterministic read-only discovery or with--self-testafter maintaining the script.
Related drones and stingers
- tauri-wasp-drone - Paired implementation specialist for Tauri-specific project work.
- rust-stinger - General Rust and Cargo architecture beneath Tauri integration.
- typescript-node-stinger - TypeScript boundaries, package tooling, and test infrastructure around the WebView frontend.
- svelte-stinger - Svelte 5 and SvelteKit frontend behavior when the Tauri WebView uses Svelte.
- security-stinger - Formal review of IPC authorization, filesystem and shell exposure, remote origins, credentials, and update trust.
- ci-release-stinger - CI and release workflow architecture beyond Tauri-specific bundle integration.
- dependency-audit-stinger - Dependency vulnerabilities, lockfile policy, update automation, and SBOM evidence.
Local file safety update
For O105 use bounded import, safe export and app-data uninstall. Read the 2026-10-08 digest, fill the evidence worksheet, and review the fictional plan and negative decisions. File selection is not arbitrary file authority. Require operation-specific approval, native identity/race review, bounded parsing, qualified publication and app-owned cleanup provenance. User documents/exports remain retained. Constructed cases are NOT_RUN; current runtime/plugin/OS support and native durability/uninstall proof remain consumer obligations.
Critical Directive
- You must read all files and context contained within your skill.
- In the event your core knowledge does not provide sufficient guidance you must make every attempt to search the internet, related knowledge base documentation files, and other available resources to supplement your knowledge prior to proceeding with your task.
- Additional related skills can be found here:
- rust-stinger - General Rust architecture, Cargo, async, testing, and unsafe-code guidance below the Tauri layer.
- typescript-node-stinger - TypeScript and package-tooling guidance for the frontend half of a Tauri application.
- svelte-stinger - Svelte 5 and SvelteKit guidance when that framework renders the WebView.
- security-stinger - Required first Ship Gate audit and formal review of Tauri authority and secret boundaries.
- quality-stinger - Required independent Quality gate after Security findings are resolved.
- github-repo-health-stinger - Required orchestrator-level repository-health gate before commit or push.
- ci-release-stinger - CI and release workflow architecture for signed multi-platform delivery.
- dependency-audit-stinger - Dependency, advisory, lockfile, SBOM, and provenance review.
Ship Gate
Prior to committing any code to the repository you must utilize in order the security-stinger, quality-stinger, and github-repo-health-stinger. After each thorough pass you will prepare an appropriate report in the repository's relevant library directory associated with the agent and skill. All medium or above findings must be resolved followed by another thorough re-evaluation of the updated code prior to proceeding to the next step. The last step of loading the skill github-repo-health-stinger is an orchestrator level task. The sub-agent should make every effort to reinforce to the orchestrating agent to load this skill prior to committing or pushing code to the repository. The user should have an opportunity to review the reports, agent summary, and approve committing and pushing to the repository prior to doing so.
Files in this skill
42tauri-stinger skill questions
How do I install the tauri-stinger skill in Claude Code?
Run npx degit legioncodeinc/vibe-coding-tools/plugins/backend-and-desktop-tools/skills/tauri-stinger ~/.claude/skills/tauri-stinger. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the tauri-stinger skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
How does it handle AI integration?
The skill provides guidance on choosing AI topologies such as hosted-provider, local-sidecar, native-runtime, or mobile-plugin architectures.
Is it suitable for general Rust development?
No, for general Rust, Cargo, or async architecture unrelated to Tauri, you should use the rust-stinger skill.