tauri-stinger — Claude Code skill for Tauri 2
tauri-stinger guides Tauri 2 desktop and mobile work, from project inspection and migration to testing and release. Use it when a change depends on Tauri-specific behavior.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install backend-and-desktop-tools@wasp-nestWhat tauri-stinger does
The skill walks through Tauri 2 work in stages: inspect the project, align component versions, then handle migration, IPC, persistence, permissions, testing, and release. An optional Python inspector produces a JSON inventory without editing project files.
Its guides also cover AI integrations, app signing, updates, and distribution for macOS, Windows, and Linux. A separate workflow checks dated references before making claims about current versions. The inspector requires Python 3.9 or later, so that step depends on having Python available; other parts of the skill do not rely on the inspector.
What it helps with
- inspect a Tauri 2 project and check its component versions
- plan a Tauri 1 to Tauri 2 migration
- design IPC commands and application state
- configure permissions, scopes, and secret boundaries
- prepare platform testing and application releases
Example prompts for the agent
- Inspect this Tauri 2 project and return a JSON inventory of its components.
- Plan the migration of this app from Tauri 1 to Tauri 2.
- Review the IPC and permissions for this app's sidecar integration.
How to install tauri-stinger
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install backend-and-desktop-tools@wasp-nestThis installs the whole backend-and-desktop-tools plugin with all its skills
2Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill tauri-stinger -a claude-code3Manually: put the files in place
~/.claude/skills/tauri-stinger/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/tauri-stinger/
1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill tauri-stinger -a codex2Manually: put the files in place
.agents/skills/tauri-stinger/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill tauri-stinger -a cursor2Manually: put the files in place
.cursor/skills/tauri-stinger/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install legioncodeinc/vibe-coding-tools plugins/backend-and-desktop-tools/skills/tauri-stinger2Manually: put the files in place
.github/skills/tauri-stinger/SKILL.md1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill tauri-stinger -a gemini-cli2Platform CLI
gemini skills install https://github.com/legioncodeinc/vibe-coding-tools --path plugins/backend-and-desktop-tools/skills/tauri-stingerManually: put the files in place
.devin/skills/tauri-stinger/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about tauri-stinger
How do I install tauri-stinger in Claude Code?
Add the marketplace with /plugin marketplace add legioncodeinc/vibe-coding-tools, then install the plugin with /plugin install backend-and-desktop-tools@wasp-nest.
What does tauri-stinger do?
It guides Tauri 2 project work, including migration, IPC, permissions, testing, signing, updates, and distribution.
Does tauri-stinger require Python?
Python 3.9 or later is needed for its optional project inspector, which creates a JSON inventory.