Tauri app frontend selection — framework choice and static export configuration
Guidance for selecting and configuring a frontend framework for Tauri v2 — Vite-by-default recommendation, SSR vs SSG decisions, static export configuration for Next.js, Nuxt, SvelteKit, Qwik, Trunk, and output-path alignment
- What
- Guidance for selecting and configuring a frontend framework for Tauri v2 — Vite-by-default recommendation, SSR vs SSG decisions, static export configuration for Next.js, Nuxt, SvelteKit, Qwik, Trunk, and output-path alignment
- Cost
- Free
- Needs
- a new Tauri v2 project where the frontend framework is undecided — the skill is a workflow guide the agent follows, not software
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @full-stack-skills' tauri-app-frontend-selection skill: guidance for choosing and configuring a frontend framework for Tauri v2 — clarifying SSR, SSG, and static-export requirements, recommending Vite by default unless SSR is genuinely required, providing static-export configuration for Next.js, Nuxt, SvelteKit, Qwik, and Trunk, and aligning output paths with Tauri asset loading, with links to the official v2.tauri.app frontend docs per framework. It produces a framework recommendation with rationale and a static-export configuration checklist, with a declared boundary (framework selection and initialization — static export configuration and output directory mapping). Honest caveats: guidance sections are bilingual English/Chinese and distinct per skill; the gotchas/workflow tail is a shared template across the tauri-app-* series; framework docs can drift with upstream releases. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a new Tauri v2 project where the frontend framework is undecided — the skill is a workflow guide the agent follows, not software Install "Tauri app frontend selection — framework choice and static export configuration" for me. It gives my agent @full-stack-skills' frontend guidance: clarify SSR/SSG/static-export requirements, recommend Vite by default unless SSR is required, provide static-export configuration for Next.js, Nuxt, SvelteKit, Qwik, and Trunk, and align output paths with Tauri asset loading — producing a framework recommendation with rationale and a static-export checklist, with links to the official v2.tauri.app frontend docs. Apache-2.0 licensed. Repository: https://github.com/full-stack-skills/tauri-skills/blob/main/skills/tauri-app-frontend-selection/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "tauri-app-frontend-selection". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing — it's a methodology; ask the agent to recommend a frontend framework for my Tauri project). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.