Tauri app develop — daily development workflow, debugging, resources, sidecar, and testing
Guidance for the Tauri v2 daily development workflow — dev server vs static assets, Rust+WebView debugging, resources and sidecar management, icons, and testing strategies (mocking, WebDriver, CI)
- What
- Guidance for the Tauri v2 daily development workflow — dev server vs static assets, Rust+WebView debugging, resources and sidecar management, icons, and testing strategies (mocking, WebDriver, CI)
- Cost
- Free
- Needs
- a Tauri v2 project in active development — the skill is a workflow guide the agent follows, not software
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @full-stack-skills' tauri-app-develop skill: guidance for the Tauri v2 daily development workflow — choosing dev-server vs static-asset mode, configuring resources, sidecars, and icons, setting up a Rust+WebView debugging flow (VS Code, RustRover, Neovim, CrabNebula devtools), and recommending testing strategies (mocking, WebDriver with Selenium/WebDriverIO examples, CI). It produces a development checklist, a debugging workflow guide, and testing recommendations, with a declared boundary (development workflow only — release builds and distribution are out of scope) and links to the official v2.tauri.app docs per topic. Honest caveats: guidance sections are bilingual English/Chinese and distinct per skill; the gotchas/workflow tail is a shared template across the tauri-app-* series; quality depends on the installed docs it references. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a Tauri v2 project in active development — the skill is a workflow guide the agent follows, not software Install "Tauri app develop — daily development workflow, debugging, resources, sidecar, and testing" for me. It gives my agent @full-stack-skills' Tauri v2 development workflow: choose dev-server vs static-asset mode, configure resources, sidecars, and icons, set up a Rust+WebView debugging flow, and apply testing strategies (mocking, WebDriver, CI) — producing a development checklist, a debugging workflow guide, and testing recommendations, with links to the official v2.tauri.app docs. Apache-2.0 licensed. Repository: https://github.com/full-stack-skills/tauri-skills/blob/main/skills/tauri-app-develop/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "tauri-app-develop". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing — it's a methodology; ask the agent about dev workflow, debugging, sidecar, or testing for my Tauri project). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.