feat: update memory debugging skill

Author: devnook

skills/memory-leak-debugging/SKILL.md

@@ -15,21 +15,23 @@ This skill provides expert guidance and workflows for finding, diagnosing, and f
 
 ## Workflows
 
-### 1. Using Memlab (Recommended)
+### 1. Capturing Snapshots
 
-When users provide `.heapsnapshot` files or want to find a memory leak, use `memlab` to automatically find memory leaks.
+When investigating a frontend web application memory leak, utilize the `chrome-devtools-mcp` tools to interact with the application and take snapshots.
+- Use tools like `click`, `navigate_page`, `fill`, etc., to manipulate the page into the desired state.
+- Revert the page back to the original state after interactions to see if memory is released.
+- Repeat the same user interactions 10 times to amplify the leak.
+- Use `take_memory_snapshot` to save `.heapsnapshot` files to disk at baseline, target (after actions), and final (after reverting actions) states.
 
-- Read [references/memlab.md](references/memlab.md) for how to use `memlab` to analyze existing heapsnapshots or run automated E2E test scenarios to find leaks.
+### 2. Using Memlab to Find Leaks (Recommended)
+
+Once you have generated `.heapsnapshot` files using `take_memory_snapshot`, use `memlab` to automatically find memory leaks.
+
+- Read [references/memlab.md](references/memlab.md) for how to use `memlab` to analyze the generated heapsnapshots.
 - Do **not** read raw `.heapsnapshot` files using `read_file` or `cat`.
 
-### 2. Identifying Common Leaks
+### 3. Identifying Common Leaks
 
 When you have found a leak trace (e.g., via `memlab` output), you must identify the root cause in the code.
 
 - Read [references/common-leaks.md](references/common-leaks.md) for examples of common memory leaks and how to fix them.
-
-### 3. Creating Memlab Scenarios
-
-To help users reproduce and test for leaks automatically, you can create a Memlab scenario file.
-
-- An example template is available at `scripts/memlab-scenario.js`.

skills/memory-leak-debugging/references/memlab.md

@@ -4,29 +4,25 @@
 
 ## Important Rule
 
-**NEVER read raw `.heapsnapshot` files directly.** They are too large and will exceed context limits. Use `memlab` commands to analyze them instead.
+**NEVER read raw `.heapsnapshot` files directly.** They are too large and will exceed context limits. Always use `memlab` commands to analyze them.
 
-## Analyzing Existing Snapshots
+## Analyzing Snapshots
 
-If the user provides 3 snapshots (baseline, target, final), you can use `memlab` to find leaks:
+You can use the `take_memory_snapshot` tool provided by the `chrome-devtools-mcp` extension to generate heap snapshots during an investigation. To find leaks, you generally need 3 snapshots:
+1.  **Baseline:** Before the suspect action.
+2.  **Target:** After the suspect action.
+3.  **Final:** After reverting the suspect action (e.g., closing a modal, navigating away).
+
+Once you have these 3 snapshots saved to disk, you can use `memlab` to find leaks:
 
 ```bash
 npx memlab find-leaks --baseline <path-to-baseline> --target <path-to-target> --final <path-to-final>
 ```
 
-You can also parse a single snapshot to find the largest objects:
+You can also parse a single snapshot to find the largest objects or explore it individually:
 
 ```bash
 npx memlab analyze snapshot --snapshot <path-to-snapshot>
 ```
 
-## Running Automated Scenarios
-
-Memlab can automatically open a browser, interact with a page, take snapshots, and find leaks.
-You need a scenario file (e.g., `scenario.js`).
-
-```bash
-npx memlab run --scenario <path-to-scenario.js>
-```
-
 Memlab will output the retainer traces for identified leaks. Use these traces to guide your search in the codebase.