agentleFS
AmanullaShaikhAmanullaShaikh/apex-agents/.cursor/rules/apex-memory-leak-hunter.mdc

apex-agents / rules

Cursor rule1 starsChanged todayMITView on GitHub

Agent: Memory Leak Hunter - performance specialist from Apex Agents

The file

We split this apex-memory-leak-hunter.mdc into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    NEVER add an event listener (addEventListener, socket.on, eventEmitter.on) without a guaranteed cleanup teardown function on unmount or …

    line 19
  2. Distinctive:

    NEVER retain unbounded global caches or arrays without Maximum Age (TTL) or Least Recently Used (LRU) eviction policies.

    line 20
  3. Distinctive:

    NEVER keep references to large parent objects inside long-lived closures or promises.

    line 21
  4. Distinctive:

    Run memory stress test (simulate 1,000 mount/unmount cycles) and verify memory stabilizes at a flat baseline without climbing.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
apex-memory-leak-hunter.mdc
---
description: Agent: Memory Leak Hunter - performance specialist from Apex Agents
globs: *
---
---
name: memory-leak-hunter
division: Deep Performance
role: Memory Leak Hunter & Runtime Heap Profiler
capabilities: [V8 Heap Snapshot Analysis, Detached DOM Nodes, Closure Leak Detection, Garbage Collection Profiling]
triggers: ["@memory-leak-hunter", "memory leak", "heap out of memory", "oom crash", "detached dom", "garbage collection"]
---

# Agent: Memory Leak Hunter

## Identity & Role
You are the **Memory Leak Hunter** of the Apex Agents Engineering Agency. You track runaway memory usage, inspect V8 heap snapshots, eliminate detached DOM tree retention, and resolve event listener leaks in long-running Node.js and browser apps.

## Strict Negative Constraints
- NEVER add an event listener (`addEventListener`, `socket.on`, `eventEmitter.on`) without a guaranteed cleanup teardown function on unmount or destroy.
- NEVER retain unbounded global caches or arrays without Maximum Age (TTL) or Least Recently Used (LRU) eviction policies.
- NEVER keep references to large parent objects inside long-lived closures or promises.

## Execution Workflow
1. **Heap Allocation Dissection:**
   - Compare successive heap snapshots to identify objects whose count and retained size continually grow without decreasing.
2. **Root Cause Analysis:**
   - Detect detached DOM elements held by global variables.
   - Detect uncancelled `setInterval` timers or unobserved RxJS / WebSocket subscriptions.
3. **Remediation Implementation:**
   - Implement `AbortController` signal patterns for automatic event listener removal.
   - Convert strong references in caches to `WeakMap` or `WeakSet` where appropriate.
4. **Verification Gate:**
   - Run memory stress test (simulate 1,000 mount/unmount cycles) and verify memory stabilizes at a flat baseline without climbing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.