tauri-app-frontend-selection
Select and configure a frontend framework for Tauri v2 with static export compatibility. Use when choosing between Vite, Next.js, Nuxt, SvelteKit, or other frameworks, configuring SSG/static export, or aligning output paths with Tauri asset loading.
Best use case
tauri-app-frontend-selection is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Select and configure a frontend framework for Tauri v2 with static export compatibility. Use when choosing between Vite, Next.js, Nuxt, SvelteKit, or other frameworks, configuring SSG/static export, or aligning output paths with Tauri asset loading.
Select and configure a frontend framework for Tauri v2 with static export compatibility. Use when choosing between Vite, Next.js, Nuxt, SvelteKit, or other frameworks, configuring SSG/static export, or aligning output paths with Tauri asset loading.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "tauri-app-frontend-selection" skill to help with this workflow task. Context: Select and configure a frontend framework for Tauri v2 with static export compatibility. Use when choosing between Vite, Next.js, Nuxt, SvelteKit, or other frameworks, configuring SSG/static export, or aligning output paths with Tauri asset loading.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/tauri-app-frontend-selection/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How tauri-app-frontend-selection Compares
| Feature / Agent | tauri-app-frontend-selection | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Select and configure a frontend framework for Tauri v2 with static export compatibility. Use when choosing between Vite, Next.js, Nuxt, SvelteKit, or other frameworks, configuring SSG/static export, or aligning output paths with Tauri asset loading.
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 mentions:**
- Frontend framework selection for a Tauri v2 app
- SSG or static export configuration for Tauri
- Vite vs SSR framework decisions
**Trigger phrases include:**
- "frontend framework", "Vite", "Next.js", "Nuxt", "SvelteKit", "SSG", "static export"
## How to use this skill
1. **Default to Vite** for most Tauri apps (best DX, no SSR complexity):
```bash
npm create tauri-app@latest -- --template react-ts # or vue-ts, svelte-ts
```
2. **For Next.js**, enable static export in `next.config.js`:
```javascript
module.exports = { output: 'export', images: { unoptimized: true } };
```
3. **For SvelteKit**, configure static adapter:
```javascript
import adapter from '@sveltejs/adapter-static';
export default { kit: { adapter: adapter({ fallback: 'index.html' }) } };
```
4. **Align output paths** in `tauri.conf.json` with the framework's build output:
```json
{ "build": { "frontendDist": "../out" } }
```
5. **Avoid SSR frameworks** unless you have a specific server-side requirement; Tauri loads local static files
6. **Verify** the build output contains an `index.html` and all assets load correctly in Tauri
## Outputs
- Framework recommendation with rationale (Vite default, SSG alternatives)
- Static export configuration for chosen framework
- Output path alignment in tauri.conf.json
## References
- https://v2.tauri.app/start/frontend/
- https://v2.tauri.app/start/frontend/nextjs/
- https://v2.tauri.app/start/frontend/sveltekit/
## Keywords
tauri frontend, vite, next.js, nuxt, sveltekit, ssg, static exportRelated Skills
tauri
Primary index and router for all Tauri v2 framework skills covering Rust backend, frontend integration, and the full plugin ecosystem. Use when any Tauri-related request is made to route to the correct specialized sub-skill with local examples and templates.
tauri-window
Create and configure Tauri v2 windows including multi-window patterns, custom titlebars, and frameless window UI. Use when creating new windows, managing window lifecycle events, implementing custom titlebar drag regions, or building multi-window architectures.
tauri-setup
Install Tauri v2 prerequisites and configure the development environment across macOS, Windows, Linux, Android, and iOS. Use when setting up Rust toolchain, Node.js, platform build tools, or mobile development prerequisites (Xcode, Android Studio).
tauri-security
Configure Tauri v2 capabilities, scoped access rules, and ACL-based permission control for production apps. Use when generating capabilities/default.json, defining scoped access per plugin, or auditing permissions for minimum-privilege compliance.
tauri-scaffold
Scaffold a Tauri v2 project with create-tauri-app, configure project structure, and set up static export for frontend frameworks. Use when creating a new project, understanding the Tauri project structure, or configuring SSG/static export for Next.js or SvelteKit.
tauri-mobile
Set up Tauri v2 for Android and iOS development including build configuration, bundle identifiers, and mobile debugging. Use when adding mobile targets to a Tauri app, configuring Android/iOS bundle IDs, or debugging on mobile devices and emulators.
tauri-ipc
Implement frontend-to-Rust IPC using invoke calls, Tauri commands, and type-safe bindings in Tauri v2. Use when defining Rust commands callable from the frontend, setting up typed IPC contracts, or implementing bidirectional event-based communication.
tauri-framework-upgrade
Migrate Tauri apps from v1 to v2 or from v2 beta to v2 stable, handling breaking changes in config, plugins, and permissions. Use when upgrading Tauri versions, resolving migration errors, or updating config/capability formats for v2.
tauri-framework-security
Harden a Tauri v2 app with baseline security controls including CSP, HTTP headers, runtime authority, and capability matrices. Use when performing security audits, configuring CSP/headers per window, or building a minimum-privilege capability matrix for production.
tauri-config
Configure tauri.conf.json for Tauri v2 apps including app metadata, build settings, plugins, CSP, and platform-specific sections. Use when editing tauri.conf.json, migrating config from v1 to v2, or setting up CSP and platform-specific configuration.
tauri-concept
Explain Tauri v2 architecture concepts including the process model, IPC isolation, and brownfield integration patterns. Use when understanding how Tauri works internally, choosing between isolation and brownfield modes, or making architecture decisions before implementation.
tauri-build
Build production-ready Tauri v2 app bundles with code signing and distribution packaging for all platforms. Use when creating release builds, configuring code signing for macOS/Windows, or setting up CI pipelines for app distribution.