/tauri-v2-integration
Implement or adjust VMark frontend <-> Tauri v2 integration. Use when adding invoke/emit bridges, menu accelerators, or IPC-related UI behaviors.
$ npx -y skills add xiaolai/vmark --skill tauri-v2-integration --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/tauri-v2-integration
Context preview
The summary Claude sees to decide when to auto-load this skill.
Implement or adjust VMark frontend <-> Tauri v2 integration. Use when adding invoke/emit bridges, menu accelerators, or IPC-related UI behaviors.
SKILL.md
tauri-v2-integration.SKILL.mdname: tauri-v2-integration description: Implement or adjust VMark frontend <-> Tauri v2 integration. Use when adding invoke/emit bridges, menu accelerators, or IPC-related UI behaviors.
Tauri v2 Integration (VMark)
Overview
Ensure Tauri v2 bridge patterns and IPC flows are consistent across frontend and Rust.
Workflow
1) Identify the bridge direction:
- Rust -> Webview: `window.emit()`/`app.emit()` + `listen()` on frontend.
- Webview -> Rust: `invoke()`.
2) Update frontend hooks/plugins that manage IPC (`src/hooks/`, `src/plugins/`). 3) Update Rust commands or menu entries in `src-tauri/`. 4) Keep behavior consistent across WYSIWYG and Source modes. 5) If E2E behavior needs validation, use Tauri MCP tools.
References
- `references/paths.md` for key files and patterns.
- Manual E2E: see `tauri-mcp-testing` skill for patterns.
Related Skills
- **`tauri-app-dev`** — General Tauri 2.0 patterns (commands, state, plugins, security)
- **`tauri-mcp-testing`** — E2E testing via Tauri MCP tools
- **`rust-tauri-backend`** — VMark Rust backend implementation
The Plain-Text Workspace Where Humans and AI Collaborate Free. Local-first. Format-aware. VMark is the plain-text workspace where humans and AI collaborate.
Repo: xiaolai/vmark
Other skills on vmark.
- /ai-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.
Open skill - /css-design-tdd
Test-driven CSS design system modifications. Run checks before/after CSS changes to verify token usage, variable definitions, fallbacks, and consistency. Use when modifying CSS tokens, fixing design inconsistencies, or auditing CSS architecture.
Open skill - /mcp-dev
Build or update MCP server/client integrations for VMark. Use when configuring MCP servers, adding MCP tools, or updating MCP-related docs and settings.
Open skill - /mcp-server-manager
Discover, register, and verify MCP servers. Use when a user asks to connect/add/install/remove an MCP server, or when you need to manage project MCP configuration.
Open skill - /plan-audit
Audit an implementation against a plan (dev-docs/plans/*). Use when a user asks to check for gaps, logic errors, or missing tests relative to a plan or Work Items.
Open skill - /plan-verify
Verify a completed implementation against a plan by running gates and checking acceptance criteria. Use when the user asks to verify work items or confirm completion.
Open skill