tauri-app-frontend-selection

When to use this skill

ALWAYS use this skill when the user mentions:

• Frontend framework selection for Tauri v2
• SSG or static export configuration for Tauri
• Vite vs SSR framework decisions

Trigger phrases include:

• "frontend selection", "Vite", "Next.js", "Nuxt", "SvelteKit", "SSG", "static export"
• "Frontend framework selection", "static export", "SSG", "Vite", "SSR"

How to use this skill

1. Clarify SSR, SSG, and static export requirements
2. Recommend Vite by default unless SSR is required
3. Provide static export configuration for Next.js, Nuxt, SvelteKit, Qwik, Trunk
4. Ensure output paths align with Tauri asset loading

Outputs

• Framework recommendation and rationale
• Static export configuration checklist

Scope

• Boundary: Frontend framework selection and initialization
• Key points: Static export configuration and output directory mapping

References

• https://v2.tauri.app/start/frontend/
• https://v2.tauri.app/start/frontend/leptos/
• https://v2.tauri.app/start/frontend/nextjs/
• https://v2.tauri.app/start/frontend/nuxt/
• https://v2.tauri.app/start/frontend/qwik/
• https://v2.tauri.app/start/frontend/sveltekit/
• https://v2.tauri.app/start/frontend/trunk/
• https://v2.tauri.app/start/frontend/vite/

Keywords

tauri frontend, vite, next.js, nuxt, ssg, static export