feat: Update skill recommendations

Author: devnook

skills/memory-leak-debugging/SKILL.md

@@ -11,7 +11,7 @@ This skill provides expert guidance and workflows for finding, diagnosing, and f
 
 - **Prefer `memlab`:** Do NOT attempt to read raw `.heapsnapshot` files directly, as they are extremely large and will consume too many tokens. Always recommend and use `memlab` to process snapshots and identify leak traces.
 - **Isolate the Leak:** Determine if the leak is in the browser (client-side) or Node.js (server-side).
-- **Common Culprits:** Look for detached DOM nodes, unhandled closures, global variables, event listeners not being removed, and caches growing unbounded.
+- **Common Culprits:** Look for detached DOM nodes, unhandled closures, global variables, event listeners not being removed, and caches growing unbounded. *Note: Detached DOM nodes are sometimes intentional caches; always ask the user before nulling them.*
 
 ## Workflows
 

skills/memory-leak-debugging/references/common-leaks.md

@@ -2,17 +2,17 @@
 
 When analyzing a retainer trace from `memlab`, look for these common patterns in the codebase:
 
-## 1. Detached DOM Nodes
+## 1. Uncleared Event Listeners
 
-A DOM node is removed from the document tree but is still referenced by a JavaScript variable.
+Event listeners attached to global objects (like `window` or `document`) or long-living objects prevent garbage collection of the objects referenced in their callbacks.
 
-**Fix:** Ensure variables holding DOM references are set to `null` when the node is removed, or limit their scope.
+**Fix:** Always call `removeEventListener` when a component unmounts or the listener is no longer needed.
 
-## 2. Uncleared Event Listeners
+## 2. Detached DOM Nodes
 
-Event listeners attached to global objects (like `window` or `document`) or long-living objects prevent garbage collection of the objects referenced in their callbacks.
+A DOM node is removed from the document tree but is still referenced by a JavaScript variable. While detachedness is a good signal for a memory leak, it's not always a bug. For example, websites sometimes intentionally cache detached navigation trees.
 
-**Fix:** Always call `removeEventListener` when a component unmounts or the listener is no longer needed.
+**Fix:** Signal the detached nodes to the user first. **Ask the user first** before nulling the references or changing the code, as the detached nodes might be part of an intentional cache. If confirmed as a leak, ensure variables holding DOM references are set to `null` when the node is removed, or limit their scope.
 
 ## 3. Unintentional Global Variables