Full-stack-skills 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.

install

source · Clone the upstream repo

git clone https://github.com/partme-ai/full-stack-skills

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/partme-ai/full-stack-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/tauri-skills/tauri-app-frontend-selection" ~/.claude/skills/partme-ai-full-stack-skills-tauri-app-frontend-selection && rm -rf "$T"

manifest: skills/tauri-skills/tauri-app-frontend-selection/SKILL.md

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

Default to Vite for most Tauri apps (best DX, no SSR complexity):

npm create tauri-app@latest -- --template react-ts  # or vue-ts, svelte-ts

For Next.js, enable static export in

next.config.js

module.exports = { output: 'export', images: { unoptimized: true } };

For SvelteKit, configure static adapter:

import adapter from '@sveltejs/adapter-static';
export default { kit: { adapter: adapter({ fallback: 'index.html' }) } };

Align output paths in

tauri.conf.json

with the framework's build output:

{ "build": { "frontendDist": "../out" } }

Avoid SSR frameworks unless you have a specific server-side requirement; Tauri loads local static files
Verify the build output contains an
```
index.html
```
and all assets load correctly in Tauri

Full-stack-skills tauri-app-frontend-selection

When to use this skill

How to use this skill

Outputs

References

Keywords