tauri
/tauri
Udostępnia wiedzę o Tauri 2: rdzeń, desktop i mobile, komendy, IPC, pluginy, OAuth i CI/CD.
- Autor
- acaprino ↗
- Repozytorium
- alfio-claude-plugins ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 27.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 25
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 7
Brak sygnałów. Repozytorium zmienione 27.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Udostępnia wiedzę o Tauri 2: rdzeń, desktop i mobile, komendy, IPC, pluginy, OAuth i CI/CD.
Oryginalny opis (EN)
Knowledge base indexing core, desktop, and mobile references. TRIGGER WHEN: working with Tauri 2 commands, IPC, plugins, project setup, OAuth, or CI/CD.
Jak działa
- Quick command reference
- Reading order by topic
- Project skeleton
- Minimum viable config
- Official docs
Podgląd SKILL.md
---
name: tauri
description: >
Knowledge base indexing core, desktop, and mobile references.
TRIGGER WHEN: working with Tauri 2 commands, IPC, plugins, project setup, OAuth, or CI/CD.
---
<daodan_host_binding host="copilot">
This binding governs execution of this package and its loaded references. It takes
precedence over executable examples written for another host. Use only registered
tools and their actual input schema; an example never creates a tool, argument,
permission, model alias or nested worker capability. Preserve the generated worker
allowlist, dependency closure, scope and delivery contracts.
Copilot binding: repository reads use search, writes use edit, shell execution uses
runCommands and network fetch uses fetch in the adapter's tool allowlist. Custom
agent dispatch uses the agent allowlist alias; the current CLI documents a task
dispatch tool. Call the mechanism actually registered in this session, not an
allowlist alias assumed to be a callable tool.
Use each registered tool's input fields; Claude's subagent_type, role and
run_in_background fields are not a portable dispatch schema. Dispatch only the
custom agent named by the generated owner-qualified binding and agents allowlist.
An omitted tools restriction retains host defaults; an explicit list constrains
the worker and does not grant omitted shell, write or MCP tools.
Skills use their exact installed registry identity; workflows are prompt entries.
A dispatched workflow also has its generated <workflow>-coordinator custom agent.
Required foreign providers use Copilot's marketplace/install commands:
copilot plugin marketplace add <source>, then copilot plugin install <provider>@<marketplace>.
Register plugin-declared MCP server commands in this host's MCP configuration as
the generated note directs. Registration and a dependency declaration alone do
not demonstrate that browser/server tools are callable by the selected worker.
Inherit the active session's model and default variant. A source model alias such
as sonnet is not a portable override; request a different model only through an
explicit adapter mapping to a valid host identity and user authorization.
Coordinator MCP allowances use <declared-server>/* for only the package's named
servers. This requires actual server registration and tool discovery; it grants
no undeclared server and does not prove MCP is callable in an installed run.
Schema reference: https://docs.github.com/en/copilot/reference/custom-agents-configuration
The executing agent and its coordinator own continuation, recovery, verification
and delivery. Skills supply knowledge and method instructions; they are not
executors or a runtime persistence mechanism.
Resolve each component by kind and exact installed identity. A role is dispatched
as a worker, a skill loads instructions, and a workflow starts its declared method.
Kernel owner-qualified skill references are logical provider identities: resolve
them to the actual host registry name and verified installed provider path. Do not
invent a registry string by adding an owner's prefix when the host does not use it.
Do not load an agent identity as a skill or execute a workflow name as a shell
command. Declared required foreign providers remain mandatory. If a required
provider or capability (including required MCP access or isolation) is unavailable,
stop its dependent phase and report the missing capability. Optional external
providers follow the method's declared selection and absence behavior; their
absence alone does not block the base workflow. Report any explicitly requested
but unavailable provider contribution as unfulfilled and continue independent
work. Do not install a different host's plugin or
substitute unrelated skills to claim coverage.
Shell execution alone does not establish interactive stdin. Before a capture or
checkpoint, use an available session-control mechanism. When stdin is unavailable,
keep user-driven capture in a supported background process with bounded output and
an explicit stop signal controlled by the coordinator after the user's completion
message. Close owned browser/process resources on completion or cancellation.
Continue working within the current authorization while the requested result is
achievable. After a tool error, inspect its cause, correct the relevant input or
implementation, retry when justified and verify the outcome; never repeat a
failing action blindly. Do not close the turn with a promise or a partial result
when an authorized next step can still produce or verify the requested result.
Stop only for a documented real impediment, a missing required capability, an
unresolved human decision or the caller's stop request. At that boundary, report
completed results, remaining work and the concrete prerequisite for continuation;
continue any independent work that the blocker does not prevent.
A tool's successful exit, a worker stop or an idle session is not the deliverable.
Return final text naming observed findings, artifact paths, executed checks and
blockers. An empty worker result is missing delivery: inspect or resume that worker
when permitted, or record failure. Verify required artifacts and candidate gates
before marking the requested outcome complete.
This is an execution binding, not a rewrite of source examples. Preserve programming
language fences, domain code and host APIs that are the subject of marketplace-ops
or agent-sdk-builder. A host-as-subject API is not a tool provided to this session.
Compiled binding and static checks do not prove an installed host executed a run.
</daodan_host_binding>
# Tauri 2 Development
Index for Tauri 2 patterns -- core, desktop, mobile. Each section points to a focused reference; the references hold gotchas and link out to canonical docs at v2.tauri.app.
## Quick command reference
| Task | Command |
|------|---------|
| New project | `npm create tauri-app@latest` |
| Add plugin | `npm run tauri add <plugin-name>` |
| Dev (desktop) | `cargo tauri dev` |
| Build (desktop) | `cargo tauri build` |
| Info / sanity check | `cargo tauri info` |
| Init Android / iOS | `npm run tauri android init` / `ios init` |
| Dev mobile | `npm run tauri android dev` / `ios dev` |
| Build APK / AAB | `npm run tauri android build --apk` / `--aab` |
| Build IPA | `npm run tauri ios build` |
## Reading order by topic
### Core
- `setup.md` -- prerequisites (Rust, Node, Vite gotchas)
- `rust-patterns.md` -- commands, state, channels, events, error handling
- `frontend-patterns.md` -- invoke, channels, listeners, capabilities
- `plugins-core.md` -- universal plugins (fs, http, store, sql, deep-link, ...)
### Desktop
- `window-management.md` -- multi-window, frameless, tray, menus, global shortcuts
- `shell-plugin.md` -- spawn child processes, sidecar binaries, scoped commands
- `build-deploy-desktop.md` -- bundling, code signing, notarization, auto-updater
- `platform-webviews.md` -- WebView2 / WKWebView / WebKitGTK differences and floors
- `authentication.md` -- OAuth/PKCE via system browser
- `ci-cd.md` -- provider-agnostic pipeline patterns
### Mobile
- `setup-mobile.md` -- Android SDK + iOS Xcode tooling, pinned versions (AGP 8.11.0 / Gradle 8.14.3 / Kotlin 1.9.25), Gradle 9.0 readiness
- `plugins-mobile.md` -- biometric, barcode, haptics, NFC, geolocation, Android safe-area workaround
- `authentication-mobile.md` -- deep-link OAuth, Apple Sign-In, Firebase callback
- `iap.md` -- in-app purchases (Google Play + App Store)
- `testing.md` -- emulator, ADB, logcat, WebView debugging (happy path)
- `debugging-mobile.md` -- iOS Web Inspector, Rust backtrace extraction, store crash logs, troubleshooting decision trees
- `mobile-stale-builds.md` -- the Cargo `rerun-if-changed` gap that ships stale frontends in APKs; `build.rs` walk pattern + Gradle safety net
- `build-deploy-mobile.md` -- signing, store builds, NDK / 16KB / RustWebViewClient gotchas
- `ci-cd-mobile.md` -- mobile signing in CI, store upload
- `distribution-android.md` -- Play Console submission, keystore, Play App Signing, common rejections
- `distribution-ios.md` -- App Store Connect, certificates and provisioning, Info.plist usage descriptions, TestFlight, App Privacy
### Specialized
- `high-frequency-ui.md` -- streaming/trading UI composition (atomic state, virtualization, rust-lld)
- `ipc-streaming.md` -- Channel-vs-emit benchmarks, rkyv zero-copy, backpressure
## Project skeleton
```
my-app/
+-- src/ # Frontend (React/Vue/Svelte/...)
+-- src-tauri/
| +-- Cargo.toml
| +-- tauri.conf.json # Main config
| +-- src/
| | +-- main.rs # Desktop entry (don't modify)
| | +-- lib.rs # All your code + mobile entry
| +-- capabilities/
| | +-- default.json # Permissions
| +-- gen/
| +-- android/ # Generated Android project
| +-- apple/ # Generated Xcode project
```
## Minimum viable config
```json
// tauri.conf.json
{
"$schema": "https://schema.tauri.app/config/2",
"productName": "MyApp",
"identifier": "com.company.myapp",
"build": {
"devUrl": "http://localhost:5173",
"frontendDist": "../dist"
}
}
```
```json
// capabilities/default.json
{ "identifier": "default", "windows": ["main"], "permissions": ["core:default"] }
```
```rust
// src-tauri/src/lib.rs
#[cfg_attr(mobile, tauri::mobile_entry_point)]
pub fn run() {
tauri::Builder::default()
.plugin(tauri_plugin_opener::init())
.invoke_handler(tauri::generate_handler![])
.run(tauri::generate_context!())
.expect("error");
}
```
## Official docs
- Tauri 2: https://v2.tauri.app
- Plugin index: https://v2.tauri.app/plugin/
- GitHub: https://github.com/tauri-apps/tauri
- Awesome Tauri (community): https://github.com/tauri-apps/awesome-tauri
Pliki w paczce (25)
- SKILL.md 10 KB
- SKILL.toml 1 KB
- references/authentication-mobile.md 17 KB
- references/authentication.md 15 KB
- references/build-deploy-desktop.md 12 KB
- references/build-deploy-mobile.md 16 KB
- references/ci-cd-mobile.md 8 KB
- references/ci-cd.md 8 KB
- references/debugging-mobile.md 21 KB
- references/distribution-android.md 16 KB
- references/distribution-ios.md 20 KB
- references/frontend-patterns.md 8 KB
- references/high-frequency-ui.md 11 KB
- references/iap.md 16 KB
- references/ipc-streaming.md 12 KB
- references/mobile-stale-builds.md 18 KB
- references/platform-webviews.md 10 KB
- references/plugins-core.md 9 KB
- references/plugins-mobile.md 10 KB
- references/rust-patterns.md 8 KB
- references/setup-mobile.md 11 KB
- references/setup.md 7 KB
- references/shell-plugin.md 9 KB
- references/testing.md 9 KB
- references/window-management.md 9 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · acaprino/alfio-claude-plugins | 100 | MIT |
| TerminalSkills/skills | 100 | Apache-2.0 |
| ericrisco/rsc-harness | 100 | MIT |
| acaprino/alfio-claude-plugins | 100 | MIT |
| acaprino/alfio-claude-plugins | 100 | MIT |
| acaprino/alfio-claude-plugins | 100 | MIT |
| acaprino/alfio-claude-plugins | 100 | MIT |
| acaprino/alfio-claude-plugins | 100 | MIT |
| claude-dev-suite/claude-dev-suite | 100 | MIT |
Identyczna treść występuje jeszcze w 1 innych folderach na GitHubie. Tu pokazujemy jedną, najlepiej ocenioną kopię.
Migawka bazy z 13.11.2026 · wersja paczki ee2c2f4d83d0 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100tauri-desktop
Prowadzi przez projekt Tauri 2.0: backend Rust z frontendem webowym, system pluginów, komendy IPC, model bezpieczeństwa, automatyczne aktualizacje i wsparcie mobilne. - 100cc-tauri-project-standard
Porządkuje pracę nad aplikacją Tauri: komendy Rust, kontrakty IPC, uprawnienia, stan i wydania na platformy. - 95desktop-tauri
Buduje bezpieczne aplikacje desktopowe i mobilne w Tauri 2: polecenia Rust, typowany IPC, uprawnienia, wtyczki i pakowanie. - 100tauri-mcp-cli
Steruje aplikacją Tauri v2 z terminala przez CLI MCP: uruchamia sesje, automatyzuje webview, zbiera stan UI i debuguje IPC. - 100tauri-stinger
Wspiera inżynierię Tauri 2 dla desktopu i mobile: aktualizacje, migracja, IPC, capabilities, sidecary, runtime'y AI, persystencja, podpisywanie, testy i dystrybucja. - 100tauri-mcp-testing
Testuje działające aplikacje Tauri end-to-end przez serwer Tauri MCP: sesje, webview, IPC, zrzuty ekranu i debugowanie.