When to use this skill
ALWAYS use this skill when the user mentions:
- CLI arguments for a Tauri application
- Schema-based argument parsing at app launch
- Routing CLI commands to app behavior or windows
Trigger phrases include:
- "cli", "arguments", "command line", "schema", "command routing", "cli plugin"
How to use this skill
- Install the CLI plugin:
cargo add tauri-plugin-cli - Define the CLI schema in
tauri.conf.json:{ "plugins": { "cli": { "description": "My Tauri App", "args": [ { "name": "input", "short": "i", "takesValue": true, "description": "Input file path" } ], "subcommands": { "open": { "description": "Open a specific view", "args": [] } } } } } - Register the plugin in your Tauri builder:
tauri::Builder::default() .plugin(tauri_plugin_cli::init()) - Handle CLI matches on the frontend:
import { getMatches } from '@tauri-apps/plugin-cli'; const matches = await getMatches(); if (matches.args.input?.value) { console.log('Input file:', matches.args.input.value); } - Combine with single-instance plugin to forward second-launch arguments to the running instance
- Configure capabilities:
"cli:default"
Outputs
- CLI argument schema in tauri.conf.json
- Frontend argument parsing and routing logic
- Second-launch argument forwarding pattern
References
- https://v2.tauri.app/plugin/cli/
Keywords
tauri cli, arguments, schema, command routing, command line