# Debug Tauri WebView Apps

Tauri WebView bugs are hard to diagnose when logs, screenshots, and runtime state are scattered. This skill gives Claude, Codex, and Claude Code a repeatable workflow for collecting evidence and writing a clear debug report.

## Install

```bash
npx skillstore add 8beeeaaat/debug-tauri
```

## Metadata

- Status: approved
- Slug: 8beeeaaat-debug-tauri
- Skillstore revision: r1
- Version status: missing
- Tree hash: 88aa2173d6ef088485a0cc28e116e7fd61a66dbb9b24f4ab254ec89f9fa85d63
- Author: 8beeeaaat
- GitHub username: 8beeeaaat
- License: MIT
- Repository: https://github.com/8beeeaaat/tauri-plugin-debug-tools/tree/main/skills/debug-tauri
- Ref: c4037264bbd363c572662d6154a3ab28f5ca4f53
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network, filesystem, external\_commands
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/8beeeaaat-debug-tauri
- Manifest: https://skillstore.pages.dev/api/skills/8beeeaaat-debug-tauri/manifest

## Capabilities

- Checks whether a named Tauri app process is running.
- Captures app screenshots through plugin APIs or legacy macOS commands.
- Finds and summarizes Tauri plugin log files across supported platforms.
- Collects WebView state details such as URL, title, user agent, and viewport.
- Validates debug setup, permissions, plugin logs, screenshots, and project structure.
- Guides creation of structured debug reports with evidence and recommended fixes.

## Use Cases

- Diagnose WebView Rendering Bugs: Collect screenshots, logs, and WebView state to understand blank screens, layout failures, or visible runtime errors.
- Validate Debug Tool Setup: Check whether logging, screenshot capture, permissions, and project structure are ready before reproducing user issues.
- Create Evidence-Based Bug Reports: Turn process data, console findings, screenshots, and state observations into a structured report for developers.

## Prompt Templates

### Check My Tauri App

```
Use the debug-tauri workflow to check whether my Tauri app is running, capture the current UI state, and summarize the first issues to inspect.
```

### Analyze Logs and Screenshot

```
Analyze the latest Tauri screenshot and plugin logs. Identify visible UI problems, recent errors, likely causes, and the next validation steps.
```

### Validate Plugin Migration

```
Review my Tauri debug setup against the migration guide. Check logging, screenshots, permissions, file locations, and remaining legacy dependencies.
```

### Build a Debug Report

```
Create a full Tauri debug report from process status, screenshot observations, log statistics, WebView state, root cause analysis, and prioritized fixes.
```

## Limitations

- The legacy capture script is macOS-only and requires screen recording permission.
- The workflow requires a Tauri app with compatible debug, log, and screenshot plugins.
- Screenshots and logs can contain sensitive data and must be reviewed before sharing.
- The skill organizes debugging evidence but does not automatically fix application bugs.

## Best Practices

- Use official Tauri plugins before legacy platform scripts whenever possible.
- Redact screenshots, logs, local paths, URLs, usernames, and command arguments before sharing a report.
- Run validation before deep debugging so missing permissions or plugins do not hide the real issue.

## Anti Patterns

- Do not capture the full monitor when an app-window capture is enough.
- Do not paste raw logs or screenshots into external systems before reviewing sensitive content.
- Do not treat a missing process or missing log file as an application bug without checking setup first.

## Security Audit

- Audited at: 2026-07-05T14:24:05.186\+00:00
- Summary: Most command-execution and hidden-path alerts are documentation examples or expected local helper-script behavior. Confirmed risk centers on screen capture, temp-stored screenshots or logs, a hidden out-of-package reference, and report workflows that can expose sensitive debugging evidence. No prompt injection attempt or network exfiltration was found in the reviewed files.

## Stats

- Views: 223
- Downloads: 9
- Favorites: 0
- Popularity score: 0