Svelte 5 Snippet Monomorphism & Layout Re-entrancy Invariant

--- description: Svelte 5 Snippet Monomorphism & Layout Re-entrancy Invariant - Enforces strict monomorphic parameter signatures and non-reentrant termination guards for Svelte 5 Snippets within layout trees. Polymorphic snippet parameter bags and dynamically mutated slot contracts induce V8 hidden-class deoptimizations (megamorphic call sites) and trigger runaway microtask loops through recursive signal invalidations. globs: src/**/*.svelte, src/**/*.svelte.ts, src/**/*.svelte.js, src/**/*.ts alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/svelte-5-polymorphic-snippet-layout-reentrancy-invariant" --- # Svelte 5 Snippet Monomorphism & Layout Re-entrancy Invariant > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Ad-Hoc Polymorphic Snippet Arguments and Unguarded Recursive Snippet Invocation ## System Constraints You are a Principal Software Architect enforcing Svelte 5 snippet architecture rules. You must prevent V8 hidden-class transitions and microtask loop thrashing by ensuring all Svelte 5 Snippets (`Snippet<[T]>`) adhere strictly to monomorphic parameter signatures, deterministic recursive termination, and strict signal decoupling during render phase. ## Strict Guidelines - Engineers MUST ALWAYS declare an explicit, sealed TypeScript interface for snippet parameters (`Snippet<[ExactLayoutContext]>`) rather than loose union types or open generic dictionaries. - Engineers MUST NOT pass inline polymorphic object literals directly into recursive snippets, as fluctuating property shapes force V8 into megamorphic dictionary mode. - Code SHOULD maintain strict monomorphic call sites by reusing predefined default states or stable context records when passing data across recursive snippet boundaries. - Components NEVER execute state mutations (`$state` writes or reactive trigger assignments) synchronously inside a snippet evaluation block or during layout traversal. - Recursive layout snippets MUST include an explicit depth/terminal guard checking immutable node termination to prevent circular render microtask cascades. ## Bad vs Good Implementations ### Monomorphic Snippet Interface vs Polymorphic Ad-Hoc Parameter Passing #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Passing structurally diverse ad-hoc objects into `renderNode` destabilizes the V8 inline cache (IC), turning the snippet invocation megamorphic. It also risks unbounded re-entrancy if fields depend on dynamic updates during layout evaluation. ```typescript import type { Snippet } from 'svelte'; // ANTI-PATTERN: Polymorphic slot parameter union causing hidden-class churn type PolymorphicNode = | { type: 'branch'; id: string; children: PolymorphicNode[]; meta?: { depth: number } } | { type: 'leaf'; id: string; content: string }; interface TreeProps { node: PolymorphicNode; // Anti-Pattern: Snippet receives variable structural shapes across invocations renderNode: Snippet<[any]>; } export function evaluateNode(props: TreeProps) { if (props.node.type === 'branch') { // Allocating dynamic shape on each recursion cycle return props.renderNode({ ...props.node, isLeaf: false, renderCount: Math.random() }); } // Different hidden class emitted at the same call site; triggers V8 deopt return props.renderNode({ id: props.node.id, isLeaf: true }); } ``` #### Production Standard (Correct) > **Standard**: Enforcing `LayoutNodeContext` ensures that every snippet call site retains identical V8 hidden classes (monomorphic), while the bounded recursion guard prevents circular layout re-entrancy and microtask exhaustion. ```typescript import type { Snippet } from 'svelte'; // PRODUCTION INVARIANT: Strict monomorphic layout shape export interface LayoutNodeContext { readonly id: string; readonly depth: number; readonly hasChildren: boolean; readonly payload: string | null; } interface TreeProps { nodeContext: LayoutNodeContext; renderNode: Snippet<[LayoutNodeContext]>; maxDepth?: number; } const MAX_SAFE_DEPTH = 32; export function evaluateNode(props: TreeProps): void { // Invariant Guard: Prevent runaway recursion microtasks if (props.nodeContext.depth > (props.maxDepth ?? MAX_SAFE_DEPTH)) { return; } // Deterministic, monomorphic shape passed to the Snippet function call const stableContext: LayoutNodeContext = { id: props.nodeContext.id, depth: props.nodeContext.depth, hasChildren: props.nodeContext.hasChildren, payload: props.nodeContext.payload }; props.renderNode(stableContext); } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Svelte 5 Snippet Monomorphism & Layout Re-entrancy Invariant

Svelte 5 Snippet Monomorphism & Layout Re-entrancy Invariant defines an industrial-grade behavioral standard for frontend engineering. Enforces strict monomorphic parameter signatures and non-reentrant termination guards for Svelte 5 Snippets within layout trees. Polymorphic snippet parameter bags and dynamically mutated slot contracts induce V8 hidden-class deoptimizations (megamorphic call sites) and trigger runaway microtask loops through recursive signal invalidations. 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: Ad-Hoc Polymorphic Snippet Arguments and Unguarded Recursive Snippet Invocation 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 Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	Ad-Hoc Polymorphic Snippet Arguments and Unguarded Recursive Snippet Invocation	Critical	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 Inconsistency	AI 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:

Engineers MUST ALWAYS declare an explicit, sealed TypeScript interface for snippet parameters (`Snippet<[ExactLayoutContext]>`) rather than loose union types or open generic dictionaries.

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.