apex-agents / rules
Cursor rule1 starsChanged todayMITView on GitHub
Agent: Memory Leak Hunter - performance specialist from Apex Agents
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,144 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository39 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/apex-api-microservices-lead.mdcCursor rule
- .cursor/rules/apex-appsec-auditor.mdcCursor rule
- .cursor/rules/apex-auth-identity-guard.mdcCursor rule
- .cursor/rules/apex-backend-systems-lead.mdcCursor rule
- .cursor/rules/apex-binary-ast-inspector.mdcCursor rule
- .cursor/rules/apex-binary-decompiler.mdcCursor rule
- .cursor/rules/apex-bundle-dietician.mdcCursor rule
- .cursor/rules/apex-ci-cd-pipeline-master.mdcCursor rule
- .cursor/rules/apex-cwv-lcp-doctor.mdcCursor rule
- .cursor/rules/apex-database-tuner.mdcCursor rule
- .cursor/rules/apex-dependency-vulnerability-scanner.mdcCursor rule
- .cursor/rules/apex-docker-slimmer.mdcCursor rule
- .cursor/rules/apex-e2e-playwright-tester.mdcCursor rule
- .cursor/rules/apex-edge-case-fuzzer.mdcCursor rule
- .cursor/rules/apex-eval-benchmarker.mdcCursor rule
- .cursor/rules/apex-event-sourcing-specialist.mdcCursor rule
- .cursor/rules/apex-ffmpeg-pipeline-master.mdcCursor rule
- .cursor/rules/apex-frontend-architect.mdcCursor rule
- .cursor/rules/apex-fullstack-general.mdcCursor rule
- .cursor/rules/apex-graphql-federation-architect.mdcCursor rule
- .cursor/rules/apex-growth-marketer.mdcCursor rule
- .cursor/rules/apex-k8s-cloud-architect.mdcCursor rule
- .cursor/rules/apex-mcp-server-builder.mdcCursor rule
- .cursor/rules/apex-network-security-auditor.mdcCursor rule
- .cursor/rules/apex-pr-artisan.mdcCursor rule
- .cursor/rules/apex-prompt-architect.mdcCursor rule
- .cursor/rules/apex-prompt-injection-shield.mdcCursor rule
- .cursor/rules/apex-rag-pipeline-architect.mdcCursor rule
- .cursor/rules/apex-readme-copywriter.mdcCursor rule
- .cursor/rules/apex-remotion-motion-engineer.mdcCursor rule
- .cursor/rules/apex-secret-leak-sentinel.mdcCursor rule
- .cursor/rules/apex-serverless-edge-lead.mdcCursor rule
- .cursor/rules/apex-sql-query-optimizer.mdcCursor rule
- .cursor/rules/apex-state-machine-architect.mdcCursor rule
- .cursor/rules/apex-system-design-architect.mdcCursor rule
- .cursor/rules/apex-tdd-champion.mdcCursor rule
- .cursor/rules/apex-typescript-pro.mdcCursor rule
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
- Very specific: line 19
NEVER add an event listener (addEventListener, socket.on, eventEmitter.on) without a guaranteed cleanup teardown function on unmount or …
- Distinctive: line 20
NEVER retain unbounded global caches or arrays without Maximum Age (TTL) or Least Recently Used (LRU) eviction policies.
- Distinctive: line 21
NEVER keep references to large parent objects inside long-lived closures or promises.
- Distinctive: line 33
Run memory stress test (simulate 1,000 mount/unmount cycles) and verify memory stabilizes at a flat baseline without climbing.
≈ “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.
Files
--- 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.
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
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.

