AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
frontendcritical PriorityID: svelte-5-runes-dynamic-signal-cleanup-invariant

Svelte 5 Runes Dynamic Signal Tree Memory Leak & Effect Disposal Invariant

Mandates deterministic teardown and lifecycle anchoring for dynamic signals, derived computations, and effects created across deeply nested component trees and state modules in Svelte 5. Prevents silent memory accumulation, detached reactive subscriber trees, and zombie microtask execution caused by uncontained signal instantiations.

Prohibited Anti-Pattern: Escaping Svelte 5 Component Effect Hierarchy via Unbound Dynamic Signals and Undisposed $effect.root Allocations

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Svelte 5 Runes Dynamic Signal Tree Memory Leak & Effect Disposal Invariant - Mandates deterministic teardown and lifecycle anchoring for dynamic signals, derived computations, and effects created across deeply nested component trees and state modules in Svelte 5. Prevents silent memory accumulation, detached reactive subscriber trees, and zombie microtask execution caused by uncontained signal instantiations.
globs: src/**/*.{svelte,svelte.ts,svelte.js,ts,js}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/svelte-5-runes-dynamic-signal-cleanup-invariant"
---

# Svelte 5 Runes Dynamic Signal Tree Memory Leak & Effect Disposal Invariant

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Escaping Svelte 5 Component Effect Hierarchy via Unbound Dynamic Signals and Undisposed $effect.root Allocations

## System Constraints
You are a Principal Frontend Architect enforcing strict memory safety and signal graph disposal invariants in Svelte 5 applications. You must enforce that all dynamic runes, derived signal trees, and effects retain explicit component lifecycle containment or deterministic teardown handlers, eliminating memory leaks caused by unbound reactive signal graphs.

## Strict Guidelines
- Engineers MUST ALWAYS return a synchronous cleanup callback from within `$effect` whenever external subscriptions, DOM listeners, timers, or manual observers are registered.
- Engineers MUST NOT instantiate `$effect` or dynamic reactive signal graphs inside asynchronous execution contexts (such as microtasks, `setTimeout`, or post-`await` continuations) without explicit containment inside an `$effect.root` boundary.
- Engineers MUST ALWAYS capture, store, and execute the disposer callback returned by `$effect.root()` when managing dynamic reactive trees outside of Svelte component initialization lifecycles.
- Code SHOULD prefer declarative `$derived` or `$derived.by` transformations over imperative state synchronization inside `$effect` to prevent dangling dependency edges in the reactive graph.
- Services MUST NEVER append component-local dynamic signals to module-scoped registries or global stores without an explicit teardown mechanism triggered on component unmount or scope destruction.
- Components NEVER instantiate dynamic ad-hoc reactive collections inside template iterations without anchoring each item's lifecycle to its corresponding key or child component boundary.

## Bad vs Good Implementations
### Dynamic Subscription and Effect Teardown in Module Service

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Creating dynamic `$state` and invoking `$effect` outside an active component initialization context without `$effect.root` causes Svelte 5 runtime warnings and prevents automatic garbage collection. The subscriber retains references in the external source, permanently leaking the signal node.
```typescript
// BAD: Instantiating unmanaged effects and dynamic signals in module scope creates memory leaks
export class DynamicMetricService {
  private registry = new Map<string, { value: number }>();

  public trackMetric(metricId: string, externalSource: { subscribe: (cb: (v: number) => void) => () => void }) {
    // Anti-pattern: Async or out-of-component effect/signal creation without boundary
    const dynamicSignal = $state({ value: 0 });
    
    // Anti-pattern: Effect created outside component tree without $effect.root leak listeners
    $effect(() => {
      const unsubscribe = externalSource.subscribe((val) => {
        dynamicSignal.value = val;
      });
      // Anti-pattern: No cleanup returned and retained indefinitely in global map
      this.registry.set(metricId, dynamicSignal);
    });
  }
}
```

#### Production Standard (Correct)
> **Standard**: Wrapping dynamically constructed reactive computations inside `$effect.root` permits fine-grained reactivity outside of typical component boundaries while providing an explicit, deterministic `cleanupRoot()` callback to de-allocate subscriber nodes and prevent memory retention.
```typescript
// GOOD: Encapsulating dynamic reactive graphs within explicit $effect.root with deterministic disposers
import { onDestroy } from 'svelte';

export interface MetricTracker {
  readonly value: number;
  dispose: () => void;
}

export class DynamicMetricService {
  public trackMetric(
    externalSource: { subscribe: (cb: (v: number) => void) => () => void }
  ): MetricTracker {
    let dynamicSignal = $state({ value: 0 });
    let teardownSource: (() => void) | null = null;

    // Explicitly anchor dynamic signal graph inside an isolated root scope
    const cleanupRoot = $effect.root(() => {
      $effect(() => {
        teardownSource = externalSource.subscribe((val) => {
          dynamicSignal.value = val;
        });
        return () => {
          teardownSource?.();
        };
      });
    });

    return {
      get value() {
        return dynamicSignal.value;
      },
      dispose: () => {
        cleanupRoot();
      }
    };
  }
}
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

Node/Browser Memory Profiler MCP
Analyzes dynamic heap allocations and uncollected signal graphs during runtime test passes.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

Svelte Compiler Diagnostic Checker
Verifies valid rune usage boundaries and component initialization lifecycle constraints across codebase.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Svelte 5 Runes Dynamic Signal Tree Memory Leak & Effect Disposal Invariant

Svelte 5 Runes Dynamic Signal Tree Memory Leak & Effect Disposal Invariant defines an industrial-grade behavioral standard for frontend engineering. Mandates deterministic teardown and lifecycle anchoring for dynamic signals, derived computations, and effects created across deeply nested component trees and state modules in Svelte 5. Prevents silent memory accumulation, detached reactive subscriber trees, and zombie microtask execution caused by uncontained signal instantiations. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Escaping Svelte 5 Component Effect Hierarchy via Unbound Dynamic Signals and Undisposed $effect.root Allocations Without an explicit system instruction file, developers spend hours debugging silent failures.
Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftEscaping Svelte 5 Component Effect Hierarchy via Unbound Dynamic Signals and Undisposed $effect.root AllocationsCritical
Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production.
Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture InconsistencyAI assistants produce mixed paradigms across files, creating fragmented codebase conventions.Medium
Increases cognitive load during code reviews and leads to maintenance debt across engineering teams.
Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.
Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

1

Engineers MUST ALWAYS return a synchronous cleanup callback from within `$effect` whenever external subscriptions, DOM listeners, timers, or manual observers are registered.

Engineers MUST ALWAYS return a synchronous cleanup callback from within `$effect` whenever external subscriptions, DOM listeners, timers, or manual observers are registered.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Engineers MUST NOT instantiate `$effect` or dynamic reactive signal graphs inside asynchronous execution contexts (such as microtasks, `setTimeout`, or post-`await` continuations) without explicit containment inside an `$effect.root` boundary.

Engineers MUST NOT instantiate `$effect` or dynamic reactive signal graphs inside asynchronous execution contexts (such as microtasks, `setTimeout`, or post-`await` continuations) without explicit containment inside an `$effect.root` boundary.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Engineers MUST ALWAYS capture, store, and execute the disposer callback returned by `$effect.root()` when managing dynamic reactive trees outside of Svelte component initialization lifecycles.

Engineers MUST ALWAYS capture, store, and execute the disposer callback returned by `$effect.root()` when managing dynamic reactive trees outside of Svelte component initialization lifecycles.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Code SHOULD prefer declarative `$derived` or `$derived.by` transformations over imperative state synchronization inside `$effect` to prevent dangling dependency edges in the reactive graph.

Code SHOULD prefer declarative `$derived` or `$derived.by` transformations over imperative state synchronization inside `$effect` to prevent dangling dependency edges in the reactive graph.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
5

Services MUST NEVER append component-local dynamic signals to module-scoped registries or global stores without an explicit teardown mechanism triggered on component unmount or scope destruction.

Services MUST NEVER append component-local dynamic signals to module-scoped registries or global stores without an explicit teardown mechanism triggered on component unmount or scope destruction.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
6

Components NEVER instantiate dynamic ad-hoc reactive collections inside template iterations without anchoring each item's lifecycle to its corresponding key or child component boundary.

Components NEVER instantiate dynamic ad-hoc reactive collections inside template iterations without anchoring each item's lifecycle to its corresponding key or child component boundary.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is Svelte 5 Runes Dynamic Signal Tree Memory Leak & Effect Disposal Invariant critical for AI coding assistants?

Mandates deterministic teardown and lifecycle anchoring for dynamic signals, derived computations, and effects created across deeply nested component trees and state modules in Svelte 5. Prevents silent memory accumulation, detached reactive subscriber trees, and zombie microtask execution caused by uncontained signal instantiations. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Escaping Svelte 5 Component Effect Hierarchy via Unbound Dynamic Signals and Undisposed $effect.root Allocations) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related FRONTEND Rules

View all rules →
frontend
119

SolidStart 1.0 Server Functions & Async Boundaries Production Standard

SolidStart 1.0 relies on the Vinxi bundler to split `server$` closures into independent HTTP POST RPC endpoints. Direct lexical closure over client signals within `server$` scopes or failure to demarcate async boundaries with `<Suspense>` causes silent serialization failures, client-bundle secret leaks, and SSR hydration mismatches. Enforcing strict parameter passing, runtime input validation, and Solid async primitives maintains security and fine-grained reactivity across network boundaries.

frontend
119

Astro 5 Actions & Content Layer Production Standard

Enforces strict type safety and architectural correctness for Astro 5 Server Actions and the zero-waterfall Content Layer API. Prevents runtime contract mismatches, hydration mismatches, and unhandled mutation exceptions across dynamic and prerendered boundaries. Failure to follow these patterns leads to silent data fetching waterfalls, build-time cache corruptions, and unhandled server action exceptions.

frontend
51

Nuxt 4 Nitro Server Engine & Shared Directory Production Standard

Nuxt 4 enforces strict boundary segregation between client UI in the app/ directory, backend endpoints in server/, and universal contracts in shared/. Violating cross-boundary isolation or maintaining module-scoped state in Nitro server handlers causes catastrophic cross-request data corruption and hydration mismatches under concurrent production traffic. Architects must enforce request-isolated H3 event contexts, universal serialization schemas, and strict path-alias boundaries.

1 Rule in Stack

Svelte