Memory Leak Debugging

This one walks you through finding and fixing memory leaks in JavaScript and Node.js apps. It's opinionated about not reading raw heapsnapshot files directly because they'll blow up your token budget, instead pushing you toward memlab for analysis. The workflow is solid: use chrome-devtools-mcp to capture snapshots at baseline, after triggering the leak, and after cleanup, then let memlab find the leak traces automatically. It includes fallback scripts if memlab isn't available and references for common culprits like detached DOM nodes, uncleaned event listeners, and unbounded caches. Helpful that it reminds you detached DOM nodes aren't always bugs since they're sometimes intentional caches.