SKILL: TROUBLESHOOTING & ISSUE RESOLUTION

STEP 1: CHECK KNOWN ISSUES FIRST

Before trying random solutions: search .agents/troubleshooting/known-issues.yaml.

WebView symptom shortcuts:

• Black screen → webview-007 / webview-010
• Messy / unstyled / overlapping HTML → webview-011 (resolutions/webview-011-unstyled-external-css.md)
• Knob dots, no arcs → webview-008

# Search known issues database
$errorPattern = "duplicate target juce"
$knownIssues = Get-Content ..claude\troubleshooting\known-issues.yaml | ConvertFrom-Yaml

$matches = $knownIssues.issues | Where-Object {
    $_.error_patterns -match $errorPattern
}

if ($matches) {
    Write-Host "✓ Known issue found: $($matches.title)"
    Write-Host "Resolution: $($matches.resolution_file)"
    
    # Load and apply solution
    Get-Content "..claude\troubleshooting\$($matches.resolution_file)"
}

STEP 2: ATTEMPT RESOLUTION

[Your existing troubleshooting steps]

STEP 3: AUTO-CAPTURE NEW ISSUES

If after 3 attempts you haven't solved it:

# Create new issue entry
$newIssue = @{
    id = "cmake-$(Get-Random -Max 999)"
    title = "[Auto-generated from error]"
    category = "build"
    severity = "high"
    symptoms = @($errorMessage)
    resolution_status = "investigating"
}

# Append to known-issues.yaml

STEP 4: DOCUMENT SOLUTION

Once resolved:

# Update status to "solved"
# Fill out resolution document with:
# - What worked
# - Why it worked
# - How to prevent it