Full-stack-skills tauri-build

Build production-ready Tauri v2 app bundles with code signing and distribution packaging for all platforms. Use when creating release builds, configuring code signing for macOS/Windows, or setting up CI pipelines for app distribution.

install

source · Clone the upstream repo

git clone https://github.com/partme-ai/full-stack-skills

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/partme-ai/full-stack-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/tauri-skills/tauri-build" ~/.claude/skills/partme-ai-full-stack-skills-tauri-build && rm -rf "$T"

manifest: skills/tauri-skills/tauri-build/SKILL.md

When to use this skill

ALWAYS use this skill when the user mentions:

Production builds or release packaging
Code signing for macOS, Windows, or Linux
CI/CD pipelines for app distribution

Trigger phrases include:

"build", "release", "signing", "distribution", "packaging", "installer", "dmg", "msi"

How to use this skill

Create a production build:

npm run tauri build

Build output is located in
```
src-tauri/target/release/bundle/
```
with platform-specific installers:
- macOS:
```
.dmg
```
  ,
```
.app
```
  bundle
- Windows:
```
.msi
```
  ,
```
.exe
```
  (NSIS)
- Linux:
```
.deb
```
  ,
```
.rpm
```
  ,
```
.AppImage
```

Configure signing in environment variables:

# macOS
export APPLE_SIGNING_IDENTITY="Developer ID Application: Your Name"
# Windows
export TAURI_SIGNING_PRIVATE_KEY="path/to/key"

Set bundle identifiers in

tauri.conf.json

{ "identifier": "com.example.myapp", "bundle": { "icon": ["icons/icon.png"] } }

Set up GitHub Actions for CI/CD using the official Tauri publish action
Validate artifacts by testing installers on each target platform before release

Full-stack-skills tauri-build

When to use this skill

How to use this skill

Outputs

References

Keywords