AI Agent Skill HUB
multiAI Summary Pending

tauri-app-planning

Plan and architect Tauri 2.0 applications from requirements to implementation, including plugin selection, capability design, and state management. Use when starting a new Tauri project, creating a technical roadmap, or mapping features to specific tauri-app-* plugins.

223 stars
bypartme-ai
View on GitHubInstallation ↓

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/tauri-app-planning/SKILL.md --create-dirs "https://raw.githubusercontent.com/partme-ai/full-stack-skills/main/skills/tauri-skills/tauri-app-planning/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/tauri-app-planning/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How tauri-app-planning Compares

Feature / Agenttauri-app-planningStandard Approach
Platform SupportmultiLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Plan and architect Tauri 2.0 applications from requirements to implementation, including plugin selection, capability design, and state management. Use when starting a new Tauri project, creating a technical roadmap, or mapping features to specific tauri-app-* plugins.

Which AI agents support this skill?

This skill is compatible with multi.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

## When to use this skill

**ALWAYS use this skill when the user:**
- Wants to start a new Tauri project and needs a plan
- Asks for a "plan", "roadmap", or "architecture" for a Tauri app
- Needs to map requirements to specific Tauri features/plugins
- Asks about orchestrating windows, state, or events

**Trigger phrases include:**
- "plan tauri app", "architecture", "roadmap", "what plugins do I need", "design"

## How to use this skill

1. **Requirement Analysis**: Clarify what the user wants to build:
   - Target platforms (macOS, Windows, Linux, Android, iOS)
   - Core features (file access, database, notifications, etc.)
   - UI framework preference (React, Vue, Svelte, etc.)
2. **Plugin Selection**: Map features to `tauri-app-*` plugins:
   ```
   File storage    → tauri-app-file-system + tauri-app-store
   Database        → tauri-app-sql (SQLite/Postgres/MySQL)
   Authentication  → tauri-app-biometric + tauri-app-stronghold
   System tray     → tauri-app-system-tray + tauri-app-positioner
   Auto-update     → tauri-app-updater
   ```
3. **Architecture Decision**: Define the app structure:
   - Monolith vs sidecar pattern
   - Multi-window topology
   - State management (Rust-managed vs frontend state)
4. **Security Scope**: Build a capability matrix mapping features to minimal permissions
5. **Execution Plan**: Generate a step-by-step implementation checklist

## Outputs

- Technical design document with stack, plugins, and architecture
- Plugin-to-feature mapping table
- Capability matrix with minimal-privilege permissions
- Ordered implementation checklist

## References

- https://v2.tauri.app/
- https://v2.tauri.app/start/

## Keywords

tauri planning, architecture, roadmap, plugin selection, project design