About tauri-v2-integration
A Tauri v2 integration skill for VMark that helps keep bridge patterns and IPC flows consistent between the frontend and Rust. It covers two-way communication, command and menu updates, and behavior across WYSIWYG and Source modes.
Key features
- 01Map Rust and WebView communication directions
- 02Maintain frontend IPC hooks and plugins
- 03Update Rust commands and menu entries
- 04Keep both editing modes consistent
- 05Use Tauri MCP tools for E2E validation
Use cases
- 01Adjust frontend-to-Rust IPC flows
- 02Modify Tauri commands or menus
- 03Check consistency between WYSIWYG and Source modes
MCP support
The skill points to Tauri MCP tools for end-to-end validation; it does not state that it provides an MCP server.
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ xiaolai/ vmark --skill tauri-v2-integrationAfter installing, type/tauri-v2-integrationin Claude Code to confirm it loaded.
Bundled filesreferences/paths.mdscripts/scan_ipc.sh
Details
From the project READMETauri v2 Integration (VMark)
Overview
Ensure Tauri v2 bridge patterns and IPC flows are consistent across frontend and Rust.
Workflow
- Identify the bridge direction:
- Rust -> Webview:
window.emit()/app.emit()+listen()on frontend. - Webview -> Rust:
invoke().
- Rust -> Webview:
- Update frontend hooks/plugins that manage IPC (
src/hooks/,src/plugins/). - Update Rust commands or menu entries in
src-tauri/. - Keep behavior consistent across WYSIWYG and Source modes.
- If E2E behavior needs validation, use Tauri MCP tools.
References
references/paths.mdfor key files and patterns.- Manual E2E: see
tauri-mcp-testingskill for patterns.
Related Skills
tauri-app-dev— General Tauri 2.0 patterns (commands, state, plugins, security)tauri-mcp-testing— E2E testing via Tauri MCP toolsrust-tauri-backend— VMark Rust backend implementation
Comments
Markdown supported