Full-stack-skills tauri-app-wasm

Compile Rust code to WebAssembly and run it in the Tauri v2 frontend for high-performance computation. Use when offloading CPU-intensive work to WASM in the WebView, deciding between WASM vs IPC for Rust logic, or optimizing frontend performance with Rust-compiled modules.

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-app-wasm" ~/.claude/skills/partme-ai-full-stack-skills-tauri-app-wasm && rm -rf "$T"

manifest: skills/tauri-skills/tauri-app-wasm/SKILL.md

When to use this skill

ALWAYS use this skill when the user mentions:

Running Rust code as WASM in the Tauri frontend
WASM vs IPC performance trade-offs
High-performance frontend computation

Trigger phrases include:

"WASM", "WebAssembly", "wasm-pack", "Rust in browser", "frontend performance"

How to use this skill

Set up a WASM crate alongside your Tauri project:

cargo install wasm-pack
wasm-pack new my-wasm-lib

Build Rust code to WASM:

wasm-pack build --target web my-wasm-lib

Import the WASM module in your frontend:

import init, { process_data } from '../my-wasm-lib/pkg';
await init();
const result = process_data(inputBuffer);

Choose WASM vs IPC:
- Use WASM for CPU-bound computation that doesn't need system APIs (image processing, crypto, parsing)
- Use IPC (invoke) for anything requiring OS access (file system, network, notifications)
Monitor bundle size impact -- WASM modules add to the frontend bundle
Benchmark to verify WASM gives measurable performance gains over JavaScript

Full-stack-skills tauri-app-wasm

When to use this skill

How to use this skill

Outputs

References

Keywords