Expert guidance for developing, testing, and deploying mobile applications with Tauri 2. Use when working with Tauri 2 mobile development for Android/iOS, including project setup, Rust backend patterns, frontend integration, plugin usage (biometric, geolocation, notifications, IAP), emulator/ADB testing, code signing, and Play Store/App Store deployment.
/plugin marketplace add acaprino/alfio-claude-plugins/plugin install tauri-development@alfio-claude-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/build-deploy.mdreferences/ci-cd.mdreferences/frontend-patterns.mdreferences/iap.mdreferences/plugins.mdreferences/rust-patterns.mdreferences/setup.mdreferences/testing.mdBuild cross-platform mobile apps with Tauri 2 using web technologies (HTML/CSS/JS) for UI and Rust for native backend.
| Task | Command |
|---|---|
| Init mobile | npm run tauri android init / npm run tauri ios init |
| Dev Android | npm run tauri android dev |
| Dev iOS | npm run tauri ios dev |
| Build APK | npm run tauri android build --apk |
| Build AAB | npm run tauri android build --aab |
| Build iOS | npm run tauri ios build |
| Add plugin | npm run tauri add <plugin-name> |
npm create tauri-app@latest with mobile targetstauri.conf.json with app identifieradb logcat | grep -iE "(tauri|RustStdout)" for logsmy-app/
├── src/ # Frontend
├── src-tauri/
│ ├── Cargo.toml
│ ├── tauri.conf.json # Main config
│ ├── src/
│ │ ├── main.rs # Desktop entry (don't modify)
│ │ └── lib.rs # Main code + mobile entry
│ ├── capabilities/
│ │ └── default.json # Permissions
│ └── gen/
│ ├── android/ # Android Studio project
│ └── apple/ # Xcode project
{
"$schema": "https://schema.tauri.app/config/2",
"productName": "MyApp",
"identifier": "com.company.myapp",
"bundle": {
"iOS": { "minimumSystemVersion": "14.0" },
"android": { "minSdkVersion": 24 }
}
}
{
"identifier": "default",
"windows": ["main"],
"permissions": ["core:default"]
}
#[cfg_attr(mobile, tauri::mobile_entry_point)]
pub fn run() {
tauri::Builder::default()
.plugin(tauri_plugin_shell::init())
.invoke_handler(tauri::generate_handler![greet])
.run(tauri::generate_context!())
.expect("error");
}
#[tauri::command]
fn greet(name: &str) -> String {
format!("Hello, {}!", name)
}
| Problem | Solution |
|---|---|
| White screen | Check JS console, verify devUrl, check capabilities |
| iOS won't connect | Use --force-ip-prompt, select IPv6 |
| INSTALL_FAILED_ALREADY_EXISTS | adb uninstall com.your.app |
| Emulator not detected | Verify adb devices, restart ADB |
| HMR not working | Configure vite.config.ts with TAURI_DEV_HOST |
See references/testing.md for detailed troubleshooting.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.