multiAI Summary Pending
tauri-app-logging
Add unified logging across Rust and frontend using the Tauri v2 logging plugin with configurable levels, filtering, and file output. Use when setting up app-wide logging, configuring log levels for dev vs release, or implementing safe diagnostics without leaking secrets.
223 stars
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/tauri-app-logging/SKILL.md --create-dirs "https://raw.githubusercontent.com/partme-ai/full-stack-skills/main/skills/tauri-skills/tauri-app-logging/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/tauri-app-logging/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How tauri-app-logging Compares
| Feature / Agent | tauri-app-logging | Standard Approach |
|---|---|---|
| Platform Support | multi | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Add unified logging across Rust and frontend using the Tauri v2 logging plugin with configurable levels, filtering, and file output. Use when setting up app-wide logging, configuring log levels for dev vs release, or implementing safe diagnostics without leaking secrets.
Which AI agents support this skill?
This skill is compatible with multi.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
## When to use this skill
**ALWAYS use this skill when the user mentions:**
- Unified logging for Tauri apps (dev and release)
- Log level configuration, filtering, or file output
- Safe diagnostics without leaking sensitive data
**Trigger phrases include:**
- "logging", "log levels", "log plugin", "diagnostics", "log file", "debug logs"
## How to use this skill
1. **Install the logging plugin**:
```bash
cargo add tauri-plugin-log
```
2. **Register the plugin** with level and target configuration:
```rust
use tauri_plugin_log::{Target, TargetKind};
tauri::Builder::default()
.plugin(tauri_plugin_log::Builder::new()
.targets([Target::new(TargetKind::Stdout), Target::new(TargetKind::LogDir { file_name: None })])
.level(log::LevelFilter::Info)
.build())
```
3. **Configure capabilities** in `src-tauri/capabilities/default.json`:
```json
{ "permissions": ["log:default"] }
```
4. **Log from the frontend**:
```typescript
import { info, warn, error } from '@tauri-apps/plugin-log';
await info('App started');
await error('Something went wrong');
```
5. **Use different log levels** for dev (Debug/Trace) vs release (Info/Warn) builds
6. **Redact sensitive data** before logging (never log tokens, passwords, or PII)
## Outputs
- Logging plugin setup with file and stdout targets
- Level-based filtering for dev vs release
- Redaction rules for sensitive data
## References
- https://v2.tauri.app/plugin/logging/
## Keywords
tauri logging, log levels, log plugin, diagnostics, log file, redaction