aiskillstore/marketplace / skills/8beeeaaat/debug-tauri
debug-tauri
VerifiedAutomates Tauri WebView debugging using official plugins (tauri-plugin-log + screenshots) with process verification, automated screenshots, console logs, and state analysis. Use when debugging Tauri apps, investigating WebView issues, analyzing runtime errors, or troubleshooting UI problems.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.8 KB |
| references/IPC_COMMANDS.md | markdown | 3.9 KB |
| references/LOGGING.md | markdown | 4.8 KB |
| references/MIGRATION.md | markdown | 10.4 KB |
| references/REFERENCE.md | markdown | 5.2 KB |
| references/REPORT_TEMPLATE.md | markdown | 3.1 KB |
| references/SCREENSHOTS.md | markdown | 4.0 KB |
| references/TROUBLESHOOTING.md | markdown | 2.8 KB |
| scripts/analyze_logs.shexecutable | script | 3.6 KB |
| scripts/capture.shexecutable | script | 2.4 KB |
| scripts/validate_setup.shexecutable | script | 4.9 KB |
| skill-report.json | config | 225.7 KB |
references/REPORT_TEMPLATE.md
View on GitHub# Debug Report Template
Use this exact structure for consistency:
````markdown
# Tauri Debug Report - [YYYY-MM-DD HH:MM]
## Screenshot

## Process Status
- Status: [Running/Not Running]
- PID: [pid]
- Memory (RSS): [MB]
- CPU: [percentage]%
- Command: [command line]
## Console Logs
### Error Count: [N]
### Warning Count: [N]
### Recent Errors
```
[error logs from last 5 entries]
```
### Recent Warnings
```
[warning logs from last 5 entries]
```
### Log Statistics
- Total logs: [N]
- Errors: [N]
- Warnings: [N]
- Info: [N]
- Debug: [N]
## WebView State
```json
{
"url": "...",
"title": "...",
"user_agent": "...",
"viewport": {
"width": ...,
"height": ...
}
}
```
## Visual Analysis
### UI State
[Description of visible UI elements, current screen, navigation state]
### Identified Issues
- [ ] Issue 1: [description with location/screenshot reference]
- [ ] Issue 2: [description with location/screenshot reference]
- [ ] Issue 3: [description with location/screenshot reference]
### Layout Problems
[Any layout issues, misalignments, overflow, or rendering problems]
### Error Indicators
[Visible error messages, banners, toast notifications, console output]
## Performance Analysis
### Memory Usage
- RSS: [MB]
- VSZ: [MB]
- Trend: [increasing/stable/decreasing]
### CPU Usage
- Current: [%]
- Average: [%]
- Spikes: [yes/no, describe if yes]
### Rendering
- FPS: [if available]
- Frame drops: [yes/no]
- GPU usage: [if available]
## Root Cause Analysis
### Primary Cause
[Analysis based on collected evidence from logs, screenshots, and state]
### Contributing Factors
1. [Factor 1]
2. [Factor 2]
3. [Factor 3]
### Evidence
- Log evidence: [specific errors/warnings]
- Visual evidence: [screenshot observations]
- State evidence: [WebView state anomalies]
## Recommendations
### Immediate Actions
1. **[Action 1]**
- Implementation: [specific code changes or commands]
- Expected outcome: [what should change]
- Risk: [low/medium/high]
2. **[Action 2]**
- Implementation: [specific code changes or commands]
- Expected outcome: [what should change]
- Risk: [low/medium/high]
### Long-term Improvements
1. [Improvement 1 with rationale]
2. [Improvement 2 with rationale]
3. [Improvement 3 with rationale]
## Next Steps
- [ ] Implement fix for [specific issue]
- [ ] Test in [environment/scenario]
- [ ] Monitor [specific metric/behavior]
- [ ] Document changes in [location]
- [ ] Verify fix with [validation method]
## Additional Notes
[Any other observations, edge cases, or relevant context]
---
**Report generated by**: [Your name/automated tool]
**Review status**: [Pending/Reviewed/Implemented]
````
## Usage Tips
1. **Fill sections progressively** as you complete each debug workflow step
2. **Be specific** in root cause analysis - avoid vague statements
3. **Include evidence** - reference specific log lines, screenshot areas
4. **Actionable recommendations** - provide exact commands or code changes
5. **Track progress** - check off items as you implement fixes
## Example Report
See `examples/sample_debug_report.md` (if created) for a filled example.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |