Tauri Desktop App taste — ChatGPT prompt: features and setup
Tauri Desktop App taste — a prompt for ChatGPT that sets engineering practices for cross-platform Tauri apps. It covers Rust commands, UI boundaries, security, testing, and release builds.
CC0-1.0 ★ 178,201 updated 2026-10-24
Open on GitHubWhat Tauri Desktop App taste does
This prompt lays out development practices for cross-platform Tauri apps. It recommends Vite and strict TypeScript for the frontend, while file, network, and OS operations belong in Rust commands. For shared Rust and TypeScript types, it names tauri-specta and ts-rs.
Its security guidance calls for per-window permissions and a strict Content Security Policy. Secrets go in the OS keychain; local data can use SQLite through sqlx or the SQL plugin, with migrations committed to the repository. Automatic updates use the updater plugin and signed release artifacts.
The prompt also covers WebDriver tests and GitHub Actions builds. macOS releases should be signed and notarized, while Windows installers should be signed in CI rather than on a developer’s machine.
What it helps with
- choose Tauri over Electron for a new desktop app
- separate Rust command logic from the UI
- set window permissions and a Content Security Policy
- build and sign releases in CI
Example prompts for the agent
- Plan a cross-platform Tauri app and split its UI from system-level logic.
- Review the security setup for my Tauri windows, including permissions and secret storage.
- Outline GitHub Actions release builds for a Tauri app on macOS and Windows.
How to install Tauri Desktop App taste
How to use
Paste the text at the start of a chat or into project instructions
Manually: put the files in place
.claude/commands/prompts.csv.mdQuestions about Tauri Desktop App taste
How do I install Tauri Desktop App taste in Claude Code?
Place the prompt file at .claude/commands/prompts.csv.md.
What does Tauri Desktop App taste do?
It sets development practices for Tauri apps, covering Rust and UI boundaries, security, testing, and release builds.
Which frontend tools does Tauri Desktop App taste recommend?
It recommends Vite and strict-mode TypeScript, with the frontend kept independent of the Rust side.
Source text
prompts.csv · CC0-1.0
# Tauri Desktop App taste of a cross-platform desktop developer - Choose Tauri over Electron for new desktop apps when bundle size and memory use matter. Confidence: 0.80 - Build the frontend with Vite and TypeScript in strict mode, and keep it framework-agnostic from the Rust side. Confidence: 0.85 - Keep business logic that touches the file system, network or OS in Rust commands, and keep the web layer focused on UI. Confidence: 0.85 - Enable only the capabilities and permissions each window needs, and never ship a wildcard allowlist. Confidence: 0.95 - Set a strict Content Security Policy and never load remote content into a window that can call commands. Confidence: 0.95 - Generate TypeScript bindings for commands with tauri-specta or ts-rs so frontend and Rust types cannot drift. Confidence: 0.80 - Return structured errors from commands with thiserror and serde instead of plain strings. Confidence: 0.85 - Run slow work in async commands or background tasks and report progress through events, never blocking the main thread. Confidence: 0.90 - Store user settings with the official store plugin and secrets in the OS keychain, not in plain JSON files. Confidence: 0.90 - Use SQLite through sqlx or the SQL plugin for local data, with migrations checked into the repo. Confidence: 0.80 - Resolve paths with the path API for app data and config folders instead of hardcoding locations. Confidence: 0.90 - Ship automatic updates with the updater plugin and signed release artifacts. Confidence: 0.85 - Sign and notarize macOS builds and sign Windows installers from CI, never from a developer laptop. Confidence: 0.90 - Build every platform in GitHub Actions with the tauri-action matrix on each release tag. Confidence: 0.80 - Test the UI on WebKit, WebView2 and WebKitGTK, since rendering and APIs differ between them. Confidence: 0.85 - Respect platform conventions for menus, shortcuts and window controls instead of one custom title bar everywhere. Confidence: 0.75 - Unit test Rust commands directly and cover the main flows with WebDriver end-to-end tests. Confidence: 0.70 - Keep the dependency tree small and run cargo audit and npm audit in CI. Confidence: 0.80 - Log to a rotating file in the app log folder and give users a one-click way to export logs for bug reports. Confidence: 0.75
© f · CC0-1.0 · f/prompts.chat