Svelte 5 Snippet Deterministic Slot Serialization and Recursive Hydration Guardrail

--- description: Svelte 5 Snippet Deterministic Slot Serialization and Recursive Hydration Guardrail - Mandates deterministic invocation, stable key identity, and symmetric SSR-to-client fallback evaluation when composing recursive and dynamic component layouts with Svelte 5 first-class snippets. Prevents fatal DOM tree divergence, unhandled hydration mismatches, and layout thrashing triggered by ambient runtime divergence or non-deterministic snippet parameter evaluation. globs: src/**/*.{svelte,svelte.ts,ts} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/svelte-5-snippet-deterministic-serialization-invariant" --- # Svelte 5 Snippet Deterministic Slot Serialization and Recursive Hydration Guardrail > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Ambient state evaluation, unkeyed recursive invocation, and asymmetric snippet fallback rendering causing SSR-to-client hydration divergence. ## System Constraints You are a Principal Software Architect enforcing absolute hydration determinism and SSR-client parity in Svelte 5 applications. You must mandate strict adherence to first-class snippet patterns: require deterministic parameter passing to snippet closures, eliminate browser/ambient state branching during initial snippet execution, enforce stable keying during recursive snippet rendering, and guarantee symmetric fallback slot resolution across SSR and hydration lifecycles. ## Strict Guidelines - Engineers MUST ALWAYS pass pure, immutable, and serializable arguments to Svelte 5 snippets (`{#snippet ...}`) to ensure identity preservation between SSR and client hydration. - Engineers MUST NOT evaluate ambient client-only state (e.g., `window`, `navigator`, `localStorage`, or dynamic date/random generators) within snippet templates during the initial render pass. - Engineers MUST ALWAYS wrap recursive snippet invocations within explicit, stably-keyed `{#each}` blocks (`{#each items as item (item.id)}`) rather than relying on index-based or unkeyed loops. - Components MUST provide explicit, deterministic fallbacks when declaring optional snippet props via `Snippet` type definitions, checking `if (snippet)` explicitly before executing `{@render snippet(...)}`. - Components NEVER render dynamic snippets that produce asymmetrical DOM structures between server-side HTML emission and client-side component mounting. - Services and component props MUST normalize recursive hierarchical structures into deterministic trees with unique, immutable node identifiers prior to snippet rendering. ## Bad vs Good Implementations ### Recursive Snippet Layout: Hydration Divergence vs Deterministic Keying #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: The snippet evaluates ambient global state (`typeof window`) during template rendering, guaranteeing an SSR-to-client markup divergence. Additionally, recursive invocation over `node.children` lacks a unique key parameter, which destabilizes DOM node reconciliation during hydration if dynamic updates occur during mount. ```svelte <script lang="ts"> import type { Snippet } from 'svelte'; interface TreeNode { id?: string; label: string; children?: TreeNode[]; } let { tree, nodeRenderer }: { tree: TreeNode[]; nodeRenderer?: Snippet<[TreeNode]> } = $props(); </script> {#snippet renderNode(node: TreeNode)} <div class="node"> {#if nodeRenderer}  {@render nodeRenderer(node)} {:else}  <span>{node.label} {typeof window !== 'undefined' ? '(Client)' : '(Server)'}</span> {/if} {#if node.children}  {#each node.children as child} {@render renderNode(child)} {/each} {/if} </div> {/snippet} {#each tree as rootNode} {@render renderNode(rootNode)} {/each} ``` #### Production Standard (Correct) > **Standard**: Eliminates all ambient runtime checks from template rendering. Enforces deterministic tree reconciliation through strictly keyed `{#each}` iterations (`(child.id)`), symmetric typed snippet parameters, and a dedicated static default snippet fallback that renders identically on both SSR and client. ```svelte <script lang="ts"> import type { Snippet } from 'svelte'; interface TreeNode { readonly id: string; readonly label: string; readonly children?: readonly TreeNode[]; } let { tree, nodeRenderer }: { tree: readonly TreeNode[]; nodeRenderer?: Snippet<[{ node: TreeNode; depth: number }]> } = $props(); </script> {#snippet defaultRenderer({ node }: { node: TreeNode; depth: number })} <span class="node-label">{node.label}</span> {/snippet} {#snippet renderBranch(node: TreeNode, depth: number)} <div class="node-container" data-node-id={node.id}> {#if nodeRenderer} {@render nodeRenderer({ node, depth })} {:else} {@render defaultRenderer({ node, depth })} {/if} {#if node.children && node.children.length > 0} <div class="node-children" role="group"> {#each node.children as child (child.id)} {@render renderBranch(child, depth + 1)} {/each} </div> {/if} </div> {/snippet} <div class="tree-root" role="tree"> {#each tree as rootNode (rootNode.id)} {@render renderBranch(rootNode, 0)} {/each} </div> ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Svelte 5 Snippet Deterministic Slot Serialization and Recursive Hydration Guardrail

Svelte 5 Snippet Deterministic Slot Serialization and Recursive Hydration Guardrail defines an industrial-grade behavioral standard for frontend engineering. Mandates deterministic invocation, stable key identity, and symmetric SSR-to-client fallback evaluation when composing recursive and dynamic component layouts with Svelte 5 first-class snippets. Prevents fatal DOM tree divergence, unhandled hydration mismatches, and layout thrashing triggered by ambient runtime divergence or non-deterministic snippet parameter evaluation. 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: Ambient state evaluation, unkeyed recursive invocation, and asymmetric snippet fallback rendering causing SSR-to-client hydration divergence. 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	Ambient state evaluation, unkeyed recursive invocation, and asymmetric snippet fallback rendering causing SSR-to-client hydration divergence.	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 pass pure, immutable, and serializable arguments to Svelte 5 snippets (`{#snippet ...}`) to ensure identity preservation between SSR and client hydration.

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.