skills_all/tauri/SKILL.md
Tauri framework for building cross-platform desktop and mobile apps. Use for desktop app development, native integrations, Rust backend, and web-based UIs.
npx skillsauth add activer007/ordinary-claude-skills tauriInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Comprehensive assistance with Tauri development, generated from official documentation.
This skill should be triggered when:
Tauri uses a Core Process (Rust) and WebView Process (HTML/CSS/JS) architecture:
Two IPC primitives:
invoke() API (WebView → Core only)[build-dependencies]
tauri-build = "2.0.0"
[dependencies]
tauri = { version = "2.0.0" }
{
"tauri": {
"bundle": {
"windows": {
"certificateThumbprint": "A1B1A2B2A3B3A4B4A5B5A6B6A7B7A8B8A9B9A0B0",
"digestAlgorithm": "sha256",
"timestampUrl": "http://timestamp.comodoca.com"
}
}
}
}
{
"version": "0.2.0",
"configurations": [
{
"type": "lldb",
"request": "launch",
"name": "Tauri Development Debug",
"cargo": {
"args": [
"build",
"--manifest-path=./src-tauri/Cargo.toml",
"--no-default-features"
]
},
"preLaunchTask": "ui:dev"
}
]
}
let data = app.state::<AppData>();
name: 'publish'
on:
push:
tags:
- 'app-v*'
# Trunk.toml
[watch]
ignore = ["./src-tauri"]
[serve]
ws_protocol = "ws"
[server.azurekv]
url = "https://<KEY_VAULT_NAME>.vault.azure.net/certificates/<CERTIFICATE_NAME>"
{
"tauri": {
"bundle": {
"windows": {
"signCommand": "relic sign -c relic.conf -f -o \"%1\""
}
}
}
}
use tauri::Manager;
#[tauri::command]
fn open_devtools(window: tauri::Window) {
window.open_devtools();
}
@Command
fun download(invoke: Invoke) {
val args = invoke.parseArgs(DownloadArgs::class.java)
// Command implementation
invoke.resolve()
}
This skill includes comprehensive documentation organized into 9 categories:
Contains: 7 pages covering foundational architecture
vscode-lldb, launch.json configuration, Windows debuggerWhen to use: Understanding Tauri's design philosophy, debugging setup, architecture decisions
Contains: 13 pages on development workflows
When to use: Setting up development environment, debugging strategies, mobile development
Contains: 8 pages on app distribution
When to use: Preparing apps for release, code signing, CI/CD pipelines, production builds
Contains: Quick start guides and initial setup instructions
When to use: Starting new Tauri projects, onboarding new developers
Contains: Plugin development and integration guides
When to use: Extending Tauri with native functionality, integrating third-party libraries
Contains: API references and configuration schemas
When to use: Looking up specific API methods, configuration properties, CLI flags
Contains: Security best practices and patterns
When to use: Hardening applications, security audits, implementing secure features
Contains: Step-by-step implementation guides
When to use: Learning by example, implementing common patterns
Contains: Miscellaneous documentation not categorized above
When to use: Troubleshooting unusual issues, platform-specific implementations
getting_started.md for project setup and basic conceptscore_concepts.md → Process Model and IPC sectionsdevelopment.md → Debug in VS Codetutorials.mdCommon beginner questions:
getting_started.mdcore_concepts.md → Process Modelcore_concepts.md → IPC → Commandsplugins.md for custom native functionalitydevelopment.md for debugging and DevToolsreference.md for API detailscore_concepts.mdCommon intermediate questions:
plugins.md → Plugin Developmentdevelopment.md → CrabNebula DevToolsreference.mdsecurity.md for production-ready securityplugins.mddistribution.mdother.mdCommon advanced questions:
distribution.md → Windows Code Signingdevelopment.md → Mobile Plugin Developmentsecurity.mdWhen asking Claude for help with Tauri:
tauri.conf.json if relevantOrganized documentation extracted from official Tauri sources (https://tauri.app/). These files contain:
Helper scripts for common automation tasks:
Add your custom scripts here for project-specific automation
Templates, boilerplate, and example projects:
Add your templates and boilerplate code here
#[tauri::command]
fn greet(name: &str) -> String {
format!("Hello, {}!", name)
}
// In main.rs
fn main() {
tauri::Builder::default()
.invoke_handler(tauri::generate_handler![greet])
.run(tauri::generate_context!())
.expect("error while running tauri application");
}
import { invoke } from '@tauri-apps/api/core';
const greeting = await invoke('greet', { name: 'World' });
console.log(greeting); // "Hello, World!"
// From Rust
app.emit_all("event-name", Payload { message: "Hello".into() }).unwrap();
// Listening in JavaScript
import { listen } from '@tauri-apps/api/event';
const unlisten = await listen('event-name', (event) => {
console.log(event.payload.message);
});
# Linux/macOS
RUST_BACKTRACE=1 tauri dev
# Windows (PowerShell)
$env:RUST_BACKTRACE=1; tauri dev
npm run tauri build -- --debug
use tauri::Manager;
window.open_devtools();
window.close_devtools();
To refresh this skill with updated documentation:
configs/tauri.jsonscripts/ and assets/tools
Generate typed TypeScript SDKs for AI agents to interact with MCP servers. Converts verbose JSON-RPC curl commands to clean function calls (docs.createDocument() vs curl). Auto-detects MCP tools from server modules, generates TypeScript types and client methods, creates runnable example scripts. Use when: building MCP-enabled applications, need typed programmatic access to MCP tools, want Claude Code to manage apps via scripts, eliminating manual JSON-RPC curl commands, validating MCP inputs/outputs, or creating reusable agent automation.
testing
Generate structured task lists from specs or requirements. IMPORTANT: After completing ANY spec via ExitSpecMode, ALWAYS ask the user: "Would you like me to generate a task list for this spec?" Use when user confirms or explicitly requests task generation from a plan/spec/PRD.
tools
Create compelling story-format summaries using UltraThink to find the best narrative framing. Support multiple formats - 3-part narrative, n-length with inline links, abridged 5-line, or comprehensive via Foundry MCP. USE WHEN user says 'create story explanation', 'narrative summary', 'explain as a story', or wants content in Daniel's conversational first-person voice.
testing
Navigate through the original three-world shamanic technology. Deploy when soul retrieval, power animal guidance, or journey between realms emerges. Deeply respectful of Tungus, Buryat, Yakut, Evenki traditions. Use for consciousness navigation, NOT cultural appropriation.