tauri

Tauri lets you build desktop (and mobile) apps with a Rust Core process and a frontend running in the OS WebView. Use these skills when scaffolding projects, wiring commands and events, configuring capabilities and permissions, or authoring plugins.

hairyf/skillsUpdated Apr 29, 2026

Works with

Claude CodeCursorClineWindsurfCodexGooseGitHub CopilotZed

1

total installs

1

this week

10

GitHub stars

0

upvotes

Install Skill

Run in your terminal

$npx skills add https://github.com/hairyf/skills --skill tauri

1

installs

1

this week

10

stars

Installation Guide

How to use tauri on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your machine
  • Node.js 16+ with npm — verify with node --version
  • Active project directory where you want to add tauri
2

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/hairyf/skills --skill tauri

Fetches tauri from hairyf/skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/tauri

Restart Cursor to activate tauri. Access via /tauri in your agent's command palette.

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

Documentation

Tauri lets you build desktop (and mobile) apps with a Rust Core process and a frontend running in the OS WebView. Use these skills when scaffolding projects, wiring commands and events, configuring capabilities and permissions, or authoring plugins.

The skill is based on Tauri v2, generated at 2026-01-30.

Core References

Topic Description Reference
Architecture Core crates, WRY/TAO, tooling, plugins core-architecture
IPC Events (fire-and-forget) vs Commands (invoke/response), when to use each core-ipc
Process Model Core process vs WebView processes, security implications core-process-model
Project Structure src-tauri layout, tauri.conf.json, capabilities, build flow core-project-structure
App Size Why small, Cargo release profile (LTO, strip, opt-level) concept-size
IPC Patterns Brownfield (default) vs Isolation (sandbox, encrypt) concept-ipc-patterns

Start

Topic Description Reference
Create Project create-tauri-app vs tauri init, dev server URL start-create-project
Prerequisites System deps, Rust, Node, WebView2, mobile (Android/iOS) start-prerequisites
Frontend Static host model, Vite/Next/Nuxt/SvelteKit/Leptos/Trunk start-frontend
Migrate Upgrading from Tauri 1.x or 2 beta, migrate command start-migrate

Develop

Topic Description Reference
Configuration Files tauri.conf.json, platform overrides, Cargo.toml, package.json develop-configuration-files
Commands #[tauri::command], invoke, args, errors, async, State, channels develop-commands
Events and Channels Emit/listen, global vs webview-specific, streaming with Channel develop-events-and-channels
State Management app.manage(), State<T> in commands, Mutex develop-state-management
Windows Creating windows (config vs WebviewWindowBuilder), label, url, visible develop-windows
Icons tauri icon command, bundle.icon, platform formats develop-icons
Resources Bundled resources, resolve path, $RESOURCE, fs permissions develop-resources
Sidecar externalBin, shell plugin, spawn from Rust/JS, permissions develop-sidecar
Debug dev vs build, Rust console, WebView devtools, RUST_BACKTRACE develop-debug
Tests Mock runtime, WebDriver E2E, CI develop-tests
Tests Mocking mockIPC, mockWindows, clearMocks (frontend tests) develop-tests-mocking
Tests WebDriver tauri-driver, platform drivers, Selenium/WebdriverIO, CI develop-tests-webdriver
Updating Dependencies npm/Cargo version sync, tauri and plugins develop-updating-dependencies
Plugins Mobile Android (Kotlin), iOS (Swift), desktop vs mobile impl develop-plugins-mobile

Security

Topic Description Reference
Capabilities Which permissions apply to which windows; capability files, remote, platforms security-capabilities
Permissions Allow/deny commands, scopes, permission sets; plugin vs app permissions security-permissions
Scopes allow/deny per command or global, path/URL patterns security-scope
CSP Content Security Policy config, script-src, style-src security-csp
HTTP Headers CORS, COOP, Permissions-Policy for webview responses security-http-headers
Runtime Authority Core enforces permissions on every invoke; denied = never run security-runtime-authority

Best Practices

Topic Description Reference
Security Lifecycle Upstream, development, build, runtime; deps, audit, dev server best-practices-security-lifecycle
Writing Plugin Permissions Autogenerated allow/deny, permission files, default set, scope schema best-practices-writing-plugin-permissions

Features

Topic Description Reference
Plugins Plugin development, lifecycle hooks, commands, permissions, state features-plugins
Official Plugins Overview dialog, fs, shell, store, updater, and others; when to use which features-official-plugins-overview
Deep Linking Custom URL scheme, App/Universal Links, single-instance + argv features-deep-linking
Updater In-app updates — check, download, install, signing, static/dynamic endpoints features-updater

Distribute

Topic Description Reference
Packaging build, bundle, installers (DMG, MSI, AppImage, etc.), signing overview distribute-packaging
Signing Code signing per platform (macOS, Windows, Linux, Android, iOS) distribute-signing
Pipelines GitHub Actions (tauri-action), CI signing, CrabNebula Cloud distribute-pipelines

Learn

Topic Description Reference
Menus and Tray Window menu, system tray, Menu/TrayIcon, predefined items learn-windows-menus-tray
Window Customization Custom titlebar, decorations, data-tauri-drag-region, transparent (macOS) learn-window-customization
Splashscreen Extra window, visible/hidden main, setup tasks, close when ready learn-splashscreen
Sidecar Node.js Node app as binary (pkg), externalBin, shell plugin learn-sidecar-nodejs
Using Plugin Permissions Add plugin, capability, allow commands, default permissions learn-using-plugin-permissions
Capabilities per Window/Platform Different capabilities per window; platforms array learn-capabilities-windows-platforms

Reference

Topic Description Reference
CLI dev, build, icon, init, migrate, bundle reference-cli
Environment Variables CI, config depth, signing, Apple/Windows/Linux, hook env reference-environment-variables
WebView Versions WebView2 (Windows), WKWebView (macOS/iOS), WebKitGTK (Linux) reference-webview-versions
Core Permissions (ACL) core:default, app, event, window, path, menu, tray, resources reference-acl-core-permissions

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Steps

  1. 1Install product management skill
  2. 2Start with user story generation for known feature
  3. 3Progress to competitive analysis: research 2-3 competitors
  4. 4Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5Draft stakeholder communications and refine based on feedback
  6. 6Build template library for recurring PM tasks
  7. 7Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use when

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid when

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Related Skills

Reviews

4.643 reviews
  • I
    Ira KhanDec 28, 2024

    Registry listing for tauri matched our evaluation — installs cleanly and behaves as described in the markdown.

  • A
    Ama SmithDec 20, 2024

    Solid pick for teams standardizing on skills: tauri is focused, and the summary matches what you get after install.

  • S
    Sakura KapoorDec 12, 2024

    tauri reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • S
    Shikha MishraDec 8, 2024

    I recommend tauri for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Y
    Yash ThakkerNov 27, 2024

    Useful defaults in tauri — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • A
    Aisha AgarwalNov 27, 2024

    We added tauri from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Z
    Zaid OkaforNov 19, 2024

    tauri fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • A
    Ava BrownNov 3, 2024

    tauri has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • A
    Ava ThompsonOct 22, 2024

    Useful defaults in tauri — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • D
    Dhruvi JainOct 18, 2024

    tauri has been reliable in day-to-day use. Documentation quality is above average for community skills.

showing 1-10 of 43

1 / 5

Discussion

Comments — not star reviews
  • No comments yet — start the thread.