Capture problem solutions in searchable knowledge base
Purpose: Automatically document solved problems to build searchable institutional knowledge with category-based organization (enum-validated problem types).
This skill captures problem solutions immediately after confirmation, creating structured documentation that serves as a searchable knowledge base for future sessions. Documentation is organized by symptom category, enabling fast lookup for VCV Rack development issues.
Why documentation matters:
When researching problems, you can quickly find solutions by symptom:
All documentation is searchable and provides forensic evidence for future development.
Auto-invoke after phrases:
OR manual: /doc-fix command
Non-trivial problems only:
Skip documentation for:
Extract from conversation history:
Required information:
Environment details:
Ask user if missing critical context:
I need a few details to document this properly:
1. Which module had this issue? [ModuleName]
2. What was the exact error message or symptom?
3. What stage were you in? (0-6 or post-implementation)
[Continue after user provides details]
Search troubleshooting/ for similar issues:
# Search by error message keywords
grep -r "exact error phrase" troubleshooting/
# Search by symptom category
ls troubleshooting/[category]/
If similar issue found:
Present options:
Found similar issue: troubleshooting/build-failures/similar-issue.md
What's next?
1. Create new doc with cross-reference (recommended)
2. Update existing doc - Add this case as variant
3. Link as duplicate - Don't create new doc
4. Other
Format: [sanitized-symptom]-[module]-[YYYYMMDD].md
Sanitization rules:
Examples:
rack-sdk-linker-error-SimpleOsc-20251112.mdsvg-panel-not-loading-WaveShaper-20251112.mdparameter-state-not-saving-Reverb-20251112.mdCRITICAL: All docs require validated YAML frontmatter with enum validation.
VCV Rack Problem Types (enums):
problem_type:
- build_error # Compilation/linking failures
- runtime_error # Crashes, exceptions during execution
- panel_issue # SVG rendering, layout problems
- cv_processing # CV signal handling issues
- dsp_issue # Audio processing problems
- parameter_issue # Module parameter bugs
- port_issue # Input/output jack problems
- performance # CPU/memory optimization
- sdk_integration # Rack SDK API misuse