skills.rest
OpenAEC-Foundation
OpenAEC-FoundationOFFICIAL
Explore all skills by this author →
GitHub

tauri-impl-migration

Migrates Tauri v1 configurations and API usage to v2 across Rust and frontend code.

4|Updated Mar 20, 2026
Search Tags:#migration#rust#tauri#tauri-migrate#v1-to-v2
One-click install
npx skills add https://github.com/OpenAEC-Foundation/OpenAEC-Workspace-Composer --skill tauri-impl-migration
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tauri-impl-migration
Source: https://github.com/OpenAEC-Foundation/OpenAEC-Workspace-Composer/tree/main/.claude/skills/tauri-2/tauri-impl/tauri-impl-migration
Command: npx skills add https://github.com/OpenAEC-Foundation/OpenAEC-Workspace-Composer --skill tauri-impl-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Upgrading Tauri from v1 to v2 can be complex due to API changes, configuration restructuring, and plugin migrations. This Skill provides a structured migration pathway with references and patterns to map old concepts to the new v2 architecture.

Core Features & Use Cases

  • API mappings: Converting v1 API usage to v2 equivalents in Rust and JavaScript.
  • Configuration migration: Translating tauri.conf.json/v1 settings to the v2 app and plugins configuration.
  • Plugin and permission migration: Registering plugins and mapping core permissions to v2 capabilities.
  • Guided upgrade examples: Includes concrete before/after patterns for windows, menus, event systems, and tray migrations.

Quick Start

Run the migration guidance on your Tauri project to start the v1 to v2 upgrade.

Frequently Asked Questions about tauri-impl-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Tauri v1 configurations to the v2 format?▼

Tauri v1 to v2 migration translates tauri.conf.json settings into the new v2 app and plugin configuration structure. It restructures configuration files and maps legacy settings to updated plugin registrations.

What does upgrading Tauri to v2 involve for Rust and frontend code?▼

Upgrading Tauri to v2 involves converting v1 API usage to v2 equivalents across Rust and JavaScript. It applies mapping rules to update API calls, event systems, and frontend integrations.

How do I handle plugin registration and permissions when upgrading to Tauri v2?▼

Tauri v2 migration registers plugins and maps core permissions to v2 capabilities. It enforces explicit permission configurations and adjusts plugin registrations within the project workflow.

Does Tauri v2 migration support multi-file project upgrades?▼

Yes, Tauri v2 migration supports multi-file project upgrades. It applies mapping rules and references migration patterns across windows, menus, event systems, and tray configurations within the project.

What are the main API changes when migrating from Tauri v1 to v2?▼

Tauri v1 to v2 API changes include configuration restructuring, plugin migration, and updates to the menu and event systems. The migration provides concrete before and after patterns for these systems.

Do I need to adjust mobile entry points when migrating to Tauri v2?▼

Yes, Tauri v2 migration enforces mobile entry adjustments as part of the upgrade workflow. It updates multi-file project configurations to ensure compatibility with the v2 architecture.

Related Skills

Explore More Software Engineering Skills→
dchukdchuk
30

customizing-tauri-windows

Implement customizable Tauri windows with titlebars, decorations, and menus.

Community
Intermediate
FirzusFirzus
1

tauri

Guide Tauri v2 command registration, IPC modeling, permissions, and debugging.

Community
Advanced
dobachidobachi

tauri-dev

Design and implement Tauri v2 apps with secure Rust core and WebView frontend.

Community
Advanced
dchukdchuk
30

migrating-tauri-apps

Migrate Tauri configurations and code from v1 or v2 beta to v2 stable.

Community
Advanced