desktop-tauri-scaffold

Scaffolds a Tauri v2 desktop app with default-deny security, updater config, and CI.

1|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/codjeremias-cell/Orquestrador-fable --skill desktop-tauri-scaffold-codjeremias-cell
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: desktop-tauri-scaffold
Source: https://github.com/codjeremias-cell/Orquestrador-fable/tree/main/skills/desktop-tauri-scaffold
Command: npx skills add https://github.com/codjeremias-cell/Orquestrador-fable --skill desktop-tauri-scaffold-codjeremias-cell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a new Tauri v2 desktop app from scratch means wiring up project structure, window capabilities, CSP, the updater, and CI by hand, where security misconfigurations are easy to introduce. This Skill generates a compiling base project with secure defaults already in place. ## Core Features & Use Cases - Project scaffolding: Delegates to create-tauri-app to generate the base structure (src/ front-end plus src-tauri/ Rust core) for React+TS+Vite or vanilla TS. - Default-deny security: Creates minimal per-window capability files and a strict CSP without unsafe-inline, unsafe-eval, or CDN-hosted assets. - Typed bridge and updater: Configures tauri-specta to export Rust types to bindings.ts and adds the updater plugin block with GitHub Releases endpoints. - Use Case: You want a lightweight desktop app (around 8 MB versus Electron's ~244 MB) for an inventory tool; the Skill produces a project that opens in dev mode, builds in CI across Windows and Linux, and is ready for a CRUD feature next. ## Quick Start Ask the assistant to scaffold a new Tauri v2 desktop app named Estoque with identifier com.jere.estoque using React and TypeScript for Windows and Linux.

Frequently Asked Questions about desktop-tauri-scaffold

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a new Tauri v2 desktop app?▼

Provide the app name, identifier (e.g., com.example.app), front-end choice (React+TS+Vite or vanilla TS), and target operating systems. The Skill delegates to create-tauri-app, then adds strict CSP, minimal capabilities, tauri-specta bindings, updater config, and a CI workflow.

Tauri vs Electron for a lightweight desktop app?▼

Tauri produces much smaller binaries (around 8 MB versus Electron's ~244 MB) and lower RAM usage by rendering with the OS WebView instead of bundling Chromium. The trade-off is that rendering can diverge across platforms since WebKit, WebView2, and Chromium differ per OS.

How does Tauri v2 default-deny security work with capabilities?▼

Each window gets a capability file in src-tauri/capabilities/ granting only the minimal scoped permissions it needs. Capabilities govern plugin and core commands plus multi-window restrictions; your own commands registered in generate_handler! are invocable without a capability entry.

Does this scaffold handle packaging and code signing?▼

No. Packaging, installer creation, and signing belong to a separate desktop-packaging step. The scaffold only adds the updater plugin block with pubkey and endpoints placeholders; the private signing key is never stored in the repo and is added later via CI secrets.

When should I use Avalonia instead of Tauri for a desktop app?▼

Choose Avalonia when friction from a JavaFX/JDBC background matters more than binary size, since XAML, C#, and ADO.NET map closely to FXML, Java, and JDBC. The stack decision is made upstream in the spec-desktop-app orchestrator before this scaffold runs.