multiAI Summary Pending
tauri-config
Configure tauri.conf.json for Tauri v2 apps including app metadata, build settings, plugins, CSP, and platform-specific sections. Use when editing tauri.conf.json, migrating config from v1 to v2, or setting up CSP and platform-specific configuration.
223 stars
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/tauri-config/SKILL.md --create-dirs "https://raw.githubusercontent.com/partme-ai/full-stack-skills/main/skills/tauri-skills/tauri-config/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/tauri-config/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How tauri-config Compares
| Feature / Agent | tauri-config | Standard Approach |
|---|---|---|
| Platform Support | multi | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Configure tauri.conf.json for Tauri v2 apps including app metadata, build settings, plugins, CSP, and platform-specific sections. Use when editing tauri.conf.json, migrating config from v1 to v2, or setting up CSP and platform-specific configuration.
Which AI agents support this skill?
This skill is compatible with multi.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
## When to use this skill
**ALWAYS use this skill when the user mentions:**
- Editing or understanding tauri.conf.json
- Config changes from Tauri v1 to v2
- CSP configuration or platform-specific config sections
**Trigger phrases include:**
- "tauri.conf.json", "tauri config", "CSP", "configuration", "build config"
## How to use this skill
1. **Understand the config structure** -- key sections of `tauri.conf.json`:
```json
{
"productName": "My App",
"version": "1.0.0",
"identifier": "com.example.myapp",
"build": {
"devUrl": "http://localhost:5173",
"frontendDist": "../dist"
},
"app": {
"windows": [{ "label": "main", "title": "My App", "width": 1024, "height": 768 }],
"security": { "csp": "default-src 'self'; script-src 'self'" }
},
"plugins": {}
}
```
2. **Configure CSP** in `app.security.csp` to restrict content loading sources
3. **Add plugin configuration** under the `plugins` key (e.g., updater endpoints, CLI schema)
4. **Platform-specific overrides** go in the appropriate config sections for Android/iOS
5. **v2 migration notes**: `tauri` key renamed to `app`, `allowlist` replaced with capabilities system, plugins moved to `plugins` key
6. **Validate config** by running `npm run tauri dev` which reports config errors on startup
## Outputs
- tauri.conf.json structure overview with key sections
- CSP configuration for content security
- v1 to v2 config migration mapping
## References
- https://v2.tauri.app/reference/config/
- https://v2.tauri.app/security/csp/
## Keywords
tauri config, tauri.conf.json, CSP, build configuration, app settings