A small starting point for cross-platform desktop apps with Tauri 2, Svelte 5 and Rust. It ships with conventions, CI and Claude Code skills already set up.
- Layered from the start. Logic lives in a plain Rust crate. The Tauri crate is a thin shell around it, and the UI talks to Rust only through commands.
- A component system for themes.
docs/themes/system.mddefines tokens and 22 core components. Each theme fills it with values, as a Markdown spec for agents plus a rendered picture for people. - Translations built in. Every string goes through
t(). To add a language, add one JSON file. - Issues for planning, ADRs for decisions. Feature, bug and ADR issue forms, plus a PR template.
- CI included. It runs
svelte-check, the frontend build,rustfmt,clippyand tests.cargo-denychecks advisories and that every dependency's license is on the allow-list indeny.toml. PR titles are checked against Conventional Commits. Dependabot is configured. - Claude Code skills.
/start-issue,/solve-adr,/open-pr,/apply-theme,/add-languageand/import-ideacover the workflow. - Briefs for outside tools. Paste-in instructions for building a theme generator or a clickable MVP prototype. Each export comes back as a theme file or as issues.
- Rust stable (pinned by
rust-toolchain.toml) - Node.js 22 or newer
- Chrome or Chromium, only to render theme pictures
- The Tauri system dependencies for your OS
cd apps/desktop
npm ci
npm run tauri dev # opens the app with hot reload
npm run tauri build # release bundle in target/release/bundle/(cd apps/desktop && npm run check)
cargo fmt --all --check
cargo clippy --workspace --all-targets -- -D warnings
cargo test --workspace
cargo deny check # advisories and licenses (cargo install --locked cargo-deny)Click Use this template on GitHub, then replace the placeholders:
| What | Where |
|---|---|
Product name App |
apps/desktop/src-tauri/tauri.conf.json (productName, window title), apps/desktop/src/app.html, app.title in apps/desktop/src/lib/i18n/en.json |
Bundle identifier com.example.app |
apps/desktop/src-tauri/tauri.conf.json |
Crate and package names app, app-core |
apps/desktop/src-tauri/Cargo.toml, crates/core/Cargo.toml, Cargo.toml, apps/desktop/package.json |
| Icons | npm run tauri icon path/to/icon.png in apps/desktop |
| Copyright holder | NOTICE.md |
| Allowed dependency licenses | deny.toml |
| Repository URL in the badges | This README |
| Theme | Copy docs/themes/default.md (or use the theme generator brief), render it, run /apply-theme <name> |
Then rewrite this README for your app.
apps/desktop/ Svelte 5 frontend (SvelteKit, static SPA)
├── src/lib/i18n/ Translation files and t()
├── src/lib/theme/ Tokens generated from the active theme
└── src-tauri/ Tauri shell crate `app`
crates/core/ Application logic, no Tauri dependency
docs/
├── adr/ Architecture decision records
├── briefs/ Instructions for building a theme generator or MVP prototype elsewhere
├── themes/ Component system, theme specs (.md) and pictures (.png)
└── languages.md Supported UI languages
tools/theme-preview/ Renders a theme's picture from its .md
.claude/skills/ Claude Code workflow skills
.github/ CI, issue forms, PR template, Dependabot
See ARCHITECTURE.md for how the parts fit together.
GitHub issues are the only planning tool. Each piece of work follows the same path:
- An issue with acceptance criteria. Use the Feature, Bug or Architecture decision form.
- A branch
<type>/<issue>-<short-name>. Run/start-issue <n>in Claude Code. - A pull request with a Conventional Commit title that closes the issue. Run
/open-pr. - A squash-merge into a protected
main.
To start from an idea rather than an issue, build a prototype with the
MVP brief and run /import-idea <file>. The export becomes
ADR questions, component issues and feature issues.
Structural decisions start as an Architecture decision issue. /solve-adr <n> takes you through
it step by step, writes the record to docs/adr/ and opens the pull request.
Details are in CONTRIBUTING.md.
| Command | What it does |
|---|---|
/start-issue <n> |
Checks the issue is ready, assigns you, creates the branch, summarises the acceptance criteria |
/solve-adr <n> |
Takes an ADR issue from question to decision with you, writes docs/adr/NNNN-*.md and opens the PR |
/open-pr |
Runs the CI checks locally, pushes and opens a PR that closes the issue |
/apply-theme [name] |
Applies a theme from docs/themes/, builds components against the system, removes hard-coded styles |
/add-language <code> |
Adds a translation file and lists it in docs/languages.md |
/import-idea <file> |
Turns an exported idea file into ADR, component and feature issues |
Agent instructions are in CLAUDE.md.
- ARCHITECTURE.md: structure and layering
- docs/adr/: decisions and why they were made
- docs/themes/: the component system, themes and the active theme
- docs/briefs/: building a theme generator or an MVP prototype outside the repo
- docs/languages.md: supported languages and translation rules
- CONTRIBUTING.md: how work gets done
Licensed under the Apache License 2.0. See NOTICE.md.