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-universal-runes-micro-frontend-reactive-boundary

Svelte 5 Universal Runes Cross-MFE Fine-Grained Reactive Boundary Protocol

Enforces fine-grained signal reactivity boundaries across micro-frontend (MFE) integrations using Svelte 5 universal runes (.svelte.ts). Prohibits coarse-grained serialized state snapshot exchange across custom element boundaries that trigger redundant Virtual DOM reconciliation passes and destroy granular signal tracking.

Prohibited Anti-Pattern: Monolithic State Snapshot Bridging Inducing Host Virtual DOM Reconciliation Cascades

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Svelte 5 Universal Runes Cross-MFE Fine-Grained Reactive Boundary Protocol - Enforces fine-grained signal reactivity boundaries across micro-frontend (MFE) integrations using Svelte 5 universal runes (.svelte.ts). Prohibits coarse-grained serialized state snapshot exchange across custom element boundaries that trigger redundant Virtual DOM reconciliation passes and destroy granular signal tracking.
globs: src/**/*.{svelte,svelte.ts,ts,js}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/svelte-5-universal-runes-micro-frontend-reactive-boundary"
---

# Svelte 5 Universal Runes Cross-MFE Fine-Grained Reactive Boundary Protocol

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Monolithic State Snapshot Bridging Inducing Host Virtual DOM Reconciliation Cascades

## System Constraints
You are a Principal Software Architect enforcing the Svelte 5 Universal Runes Reactive Boundary Protocol across micro-frontends. Ensure all cross-boundary state exchanges leverage fine-grained signal subscriptions and encapsulated universal runes (.svelte.ts) rather than triggering monolithic Virtual DOM re-renders or deep snapshot diffing in host frameworks.

## Strict Guidelines
- Engineers MUST ALWAYS isolate shared micro-frontend state within universal rune modules (`.svelte.ts`) exposing discrete signal accessors rather than dispatching monolithic object snapshots.
- Engineers MUST NOT pass whole-state JSON blobs or immutable state clones across Custom Element or Web Component boundaries when only individual property subscriptions are required.
- Code MUST consume fine-grained signal getters (`() => state.property`) when projecting Svelte 5 reactive context into non-Svelte host applications (e.g., React, Vue) to bypass top-level host component re-renders.
- Services MUST bridge cross-MFE reactive events using atomic, targeted CustomEvent notifications or shared universal Signal observables instead of global window-level broadcast buses.
- Components NEVER re-instantiate Svelte 5 root instances (`mount()`) or trigger unmount/remount cycles to synchronize external state; state updates MUST flow continuously through in-place rune references.

## Bad vs Good Implementations
### Cross-MFE State Synchronization Bridge

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Destroying and re-mounting Svelte components or deserializing full state payloads on attribute changes triggers full tree invalidation, breaks fine-grained signal graphs, and forces costly parent Virtual DOM reconciliation cycles.
```typescript
// Anti-pattern: Coarse snapshot serialization forces host VDOM tree reconciliation
import { mount } from 'svelte';
import MicroFrontendRoot from './MicroFrontendRoot.svelte';

export class UserProfileElement extends HTMLElement {
  private app: any;

  static get observedAttributes() {
    return ['user-state'];
  }

  attributeChangedCallback(name: string, oldValue: string, newValue: string) {
    if (name === 'user-state' && oldValue !== newValue) {
      // Re-mounting or passing monolithic JSON payload destroys internal signal tracking
      // and triggers full reconciliation in parent React/VDOM wrappers
      const state = JSON.parse(newValue);
      if (this.app) {
        this.app.$destroy?.();
      }
      this.app = mount(MicroFrontendRoot, {
        target: this,
        props: { fullUserState: state }
      });
    }
  }
}
```

#### Production Standard (Correct)
> **Standard**: Encapsulates reactive state inside a Svelte 5 universal rune wrapper (`.svelte.ts`), preserving signal graph granularity across Custom Element boundaries and eliminating host Virtual DOM reconciliation.
```typescript
// Production standard: Fine-grained Svelte 5 universal runes with targeted signal accessors
import { mount, unmount } from 'svelte';
import MicroFrontendRoot from './MicroFrontendRoot.svelte';
import { createCrossMfeSignal } from './userState.svelte.ts';

export class UserProfileElement extends HTMLElement {
  private app: Record<string, any> | null = null;
  private userSignal = createCrossMfeSignal({
    id: '',
    displayName: '',
    permissions: []
  });

  connectedCallback() {
    // Mount once: internal reactivity drives targeted DOM mutations without VDOM diffing
    this.app = mount(MicroFrontendRoot, {
      target: this,
      props: {
        state: this.userSignal
      }
    });
  }

  // Atomic updates bypass full serialization and trigger fine-grained signal nodes directly
  public updateDisplayName(name: string): void {
    this.userSignal.displayName = name;
  }

  public updatePermissions(permissions: string[]): void {
    this.userSignal.permissions = permissions;
  }

  disconnectedCallback() {
    if (this.app) {
      unmount(this.app);
      this.app = null;
    }
  }
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Svelte AST Analyzer
Inspects Svelte 5 rune AST nodes and flags monolithic props drilling across Custom Element boundaries.
Recommended Agent Skills (askills.dev)

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

Svelte Check CLI
Validates Svelte 5 rune declarations and strict typing across universal modules.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Svelte 5 Universal Runes Cross-MFE Fine-Grained Reactive Boundary Protocol

Svelte 5 Universal Runes Cross-MFE Fine-Grained Reactive Boundary Protocol defines an industrial-grade behavioral standard for frontend engineering. Enforces fine-grained signal reactivity boundaries across micro-frontend (MFE) integrations using Svelte 5 universal runes (.svelte.ts). Prohibits coarse-grained serialized state snapshot exchange across custom element boundaries that trigger redundant Virtual DOM reconciliation passes and destroy granular signal tracking. 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: Monolithic State Snapshot Bridging Inducing Host Virtual DOM Reconciliation Cascades 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 DriftMonolithic State Snapshot Bridging Inducing Host Virtual DOM Reconciliation CascadesCritical
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 isolate shared micro-frontend state within universal rune modules (`.svelte.ts`) exposing discrete signal accessors rather than dispatching monolithic object snapshots.

Engineers MUST ALWAYS isolate shared micro-frontend state within universal rune modules (`.svelte.ts`) exposing discrete signal accessors rather than dispatching monolithic object snapshots.

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 pass whole-state JSON blobs or immutable state clones across Custom Element or Web Component boundaries when only individual property subscriptions are required.

Engineers MUST NOT pass whole-state JSON blobs or immutable state clones across Custom Element or Web Component boundaries when only individual property subscriptions are required.

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

Code MUST consume fine-grained signal getters (`() => state.property`) when projecting Svelte 5 reactive context into non-Svelte host applications (e.g., React, Vue) to bypass top-level host component re-renders.

Code MUST consume fine-grained signal getters (`() => state.property`) when projecting Svelte 5 reactive context into non-Svelte host applications (e.g., React, Vue) to bypass top-level host component re-renders.

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

Services MUST bridge cross-MFE reactive events using atomic, targeted CustomEvent notifications or shared universal Signal observables instead of global window-level broadcast buses.

Services MUST bridge cross-MFE reactive events using atomic, targeted CustomEvent notifications or shared universal Signal observables instead of global window-level broadcast buses.

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

Components NEVER re-instantiate Svelte 5 root instances (`mount()`) or trigger unmount/remount cycles to synchronize external state

Components NEVER re-instantiate Svelte 5 root instances (`mount()`) or trigger unmount/remount cycles to synchronize external state; state updates MUST flow continuously through in-place rune references.

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 Universal Runes Cross-MFE Fine-Grained Reactive Boundary Protocol critical for AI coding assistants?

Enforces fine-grained signal reactivity boundaries across micro-frontend (MFE) integrations using Svelte 5 universal runes (.svelte.ts). Prohibits coarse-grained serialized state snapshot exchange across custom element boundaries that trigger redundant Virtual DOM reconciliation passes and destroy granular signal tracking. 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 (Monolithic State Snapshot Bridging Inducing Host Virtual DOM Reconciliation Cascades) 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