Tauri Config — tauri.conf.json structure, lifecycle, CSP and platform sections
Map app requirements to tauri.conf.json sections, apply the v2 config layout and plugin locations, validate CSP and Android/iOS/desktop platform config
- What
- Map app requirements to tauri.conf.json sections, apply the v2 config layout and plugin locations, validate CSP and Android/iOS/desktop platform config
- Cost
- Free
- Needs
- a Tauri v2 project with a tauri.conf.json to configure (or one to create)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @full-stack-skills' tauri-config: a Tauri v2 agent skill for tauri.conf.json structure, lifecycle management and CSP configuration. Trigger phrases (tauri.conf.json, config, CSP, android, ios, plus Chinese equivalents) route the agent to: identify app requirements and platform targets, map them to tauri.conf.json sections, apply the v2 config layout and plugin locations, and validate CSP and platform config for desktop and mobile. Ships with a curated reference list to the official Tauri v2 config reference and CSP docs. Honest caveats: one of five topic-specific skills from the same repo (an umbrella Tauri router listing is already on the directory); the "gotchas" and Chinese "使用流程" sections are boilerplate shared across the series — the config-specific value is the trigger phrases, the how-to steps and the docs reference list. Bilingual EN/中文. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Tauri Config is a free Tauri v2 skill from @full-stack-skills for tauri.conf.json structure, lifecycle and CSP. Triggers route to identify requirements and targets, map them to tauri.conf.json sections, apply the layout and plugin locations, and validate CSP and platform config. It ships with a reference list to the Tauri config reference and CSP docs, with bilingual English and Chinese guidance.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 77b57c4Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Tauri v2 project with a tauri.conf.json to configure (or one to create) Install "Tauri Config — tauri.conf.json structure, lifecycle, CSP and platform sections" for me. It gives my agent @full-stack-skills' config workflow: detect config intent via trigger phrases (tauri.conf.json, config, CSP, android, ios), identify app requirements and platform targets, map requirements to tauri.conf.json sections, apply the v2 config layout and plugin locations, and validate CSP and platform config for desktop and mobile, with the official Tauri v2 config reference as the source. Apache-2.0 licensed. Repository: https://raw.githubusercontent.com/full-stack-skills/tauri-skills/77b57c4913873a0f8cab7db45116038dc18a27f0/skills/tauri-config/SKILL.md Pinned version: install the code at commit 77b57c4913873a0f8cab7db45116038dc18a27f0 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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, credentials only via the secure vault, allowed hosts declared in the SKILL.md. 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-config". 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. describe my app's platforms and requirements so the agent can map them to tauri.conf.json sections; nothing else — it's a guidance skill). 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.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 77b57c4 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.