From cipherpowers
Creates symptom-based debugging documentation organized by observable symptoms for troubleshooting guides, bug documentation, and FIX/ sections.
npx claudepluginhub cipherstash/cipherpowers --plugin cipherpowersThis skill uses the workspace's default tool permissions.
Create debugging documentation organized by observable symptoms, not root causes. Developers search by what they see, not by what's wrong.
Provides 54-rule debugging methodology across 10 categories for bug reproduction, hypothesis-driven investigation, root cause analysis, and verification. Use for errors, crashes, stack traces, or incidents.
Guides debugging with 54 rules across 10 categories like problem definition, hypothesis-driven search, observation techniques, and root cause analysis. Use for bugs, errors, crashes, stack traces, segfaults, or incidents.
Captures verified solutions to non-trivial problems as categorized markdown files with YAML frontmatter in symptom directories for grep-searchable knowledge base. Auto-triggers on phrases like 'that worked' or /doc-fix command.
Share bugs, ideas, or general feedback.
Create debugging documentation organized by observable symptoms, not root causes. Developers search by what they see, not by what's wrong.
Announce at start: "I'm using the documenting-debugging-workflows skill to create symptom-based debugging docs."
Wrong: Organize by root cause (memory-leaks/, type-errors/) Right: Organize by observable symptom (visual-bugs/, slow-startup/)
Developers don't know the root cause when they start debugging - they know what they observe.
Gather observable symptoms from:
For each symptom, note:
Group symptoms by observable category:
FIX/
├── symptoms/
│ ├── visual-bugs/ # "Rendering looks wrong"
│ ├── performance/ # "It's slow"
│ ├── test-failures/ # "Tests fail"
│ ├── build-errors/ # "Won't compile"
│ └── data-issues/ # "Data is wrong"
├── investigation/
│ └── systematic-debugging.md
└── solutions/
└── common-fixes.md
Choose categories based on YOUR project's common issues.
Create the entry point with a scannable table:
# [Category] Debugging Guide
## Quick Diagnosis
| Symptom | Likely Cause | Investigation | Priority |
|---------|--------------|---------------|----------|
| [What you see] | [Root cause] | [Link] | ⚠️ High |
| [What you see] | [Root cause] | [Link] | ☠️ Critical |
Priority icons:
For each symptom, create structured documentation:
Use template: ${CLAUDE_PLUGIN_ROOT}templates/symptom-debugging-template.md
Document systematic approaches in investigation/:
Document known fixes in solutions/:
Document when to escalate:
Don't:
Do:
## Rendering Artifacts on Screen
### What You See
Flickering textures, z-fighting, or objects appearing through walls.
### Likely Causes
1. **Floating point precision** (most common)
- Objects far from origin
- Verify: Check object world coordinates
2. **Z-buffer precision**
- Near/far plane ratio too large
- Verify: Check camera settings
### Investigation Steps
1. [ ] Log object world coordinates
```rust
info!("Position: {:?}", transform.translation);
If > 10000 units from origin → floating point issue
info!("Near: {}, Far: {}", camera.near, camera.far);
If floating point: Implement floating origin If z-buffer: Adjust camera planes
## Related Skills
- **Organizing documentation:** `${CLAUDE_PLUGIN_ROOT}skills/organizing-documentation/SKILL.md`
- **Creating research packages:** `${CLAUDE_PLUGIN_ROOT}skills/creating-research-packages/SKILL.md`
- **Creating quality gates:** `${CLAUDE_PLUGIN_ROOT}skills/creating-quality-gates/SKILL.md`
## References
- Standards: `${CLAUDE_PLUGIN_ROOT}standards/documentation-structure.md`
- Template: `${CLAUDE_PLUGIN_ROOT}templates/symptom-debugging-template.md`