tauri-v2-integration
Tauri 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
More from xiaolai/vmark
tiptap-editor
Tiptap editor API patterns for vmark WYSIWYG development. Use when working with editor commands, node traversal, selection handling, or format operations.
268ai-coding-agents
Comprehensive guide for using Codex CLI (OpenAI) and Claude Code CLI (Anthropic) - AI-powered coding agents. Use when orchestrating CLI commands, automating tasks, configuring agents, or troubleshooting issues.
138tiptap-dev
Expert guidance for building rich text editors with Tiptap - a headless, framework-agnostic editor built on ProseMirror. Use when creating custom nodes, marks, or extensions for Tiptap, implementing input rules or paste rules, working with the Tiptap commands API, building React integrations with useEditor, extending existing extensions, or creating custom node views.
71tauri-app-dev
Expert guidance for building cross-platform desktop applications with Tauri 2.0 and Rust. Use when developing Tauri apps including commands and IPC, file system operations, window management, state management, system tray, menus, plugin development, security configuration (capabilities/permissions), bundling/distribution, and auto-updates. Covers patterns for editor applications requiring file dialogs, native menus, and frontend-backend communication.
67tauri-mcp-testing
E2E testing expert for Tauri applications using Tauri MCP server. Use when testing running Tauri apps - session management, webview interaction, IPC verification, screenshot capture, and debugging. ALWAYS use tauri_* tools, NEVER Chrome DevTools MCP for Tauri apps.
65rust-tauri-backend
Implement or modify VMark's Rust/Tauri backend. Use when adding Tauri commands, menu items, filesystem integration, or platform behaviors in src-tauri.
61