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: tanstack-virtual-3-windowing-performance

TanStack Virtual 3.0 Dynamic Measurement, Scroll Containment, and DOM Saturation Guardrails

Enforces strict performance invariants for TanStack Virtual 3.0 in high-density tables and lists. Prevents layout thrashing, DOM node saturation, and measurement jitter by requiring continuous measurement containment, transform-based positioning, and explicit scroll margin offsets. Mandates non-reactive scroll containers, stable item keys, and proper teardown of resize observers.

Prohibited Anti-Pattern: Uncontained Dynamic Layout Thrashing and Render-Time Item Measurement Cascades

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: TanStack Virtual 3.0 Dynamic Measurement, Scroll Containment, and DOM Saturation Guardrails - Enforces strict performance invariants for TanStack Virtual 3.0 in high-density tables and lists. Prevents layout thrashing, DOM node saturation, and measurement jitter by requiring continuous measurement containment, transform-based positioning, and explicit scroll margin offsets. Mandates non-reactive scroll containers, stable item keys, and proper teardown of resize observers.
globs: src/**/*.{ts,tsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/tanstack-virtual-3-windowing-performance"
---

# TanStack Virtual 3.0 Dynamic Measurement, Scroll Containment, and DOM Saturation Guardrails

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Uncontained Dynamic Layout Thrashing and Render-Time Item Measurement Cascades

## System Constraints
You are a Principal Engineer enforcing TanStack Virtual 3.0 Windowing Performance. Mandate invariants that prevent DOM node saturation, layout thrashing, resize observer recursion, and incorrect coordinate calculation during scrolling in massive virtualization surfaces.

## Strict Guidelines
- Engineers MUST ALWAYS attach the element measurement ref via `measureElement` callback directly to the rendered virtual row DOM node, never to child wrapper nodes or fragmented containers.
- Engineers MUST NEVER use `top` or `margin-top` for virtual item positioning; all positioning MUST use GPU-accelerated CSS `transform: translateY(...)` combined with `will-change: transform` or native absolute layout without triggering document reflow.
- Components MUST ALWAYS provide a stable, unique key to each virtual item matching `virtualItem.key` derived from data identity, NEVER relying on `virtualItem.index` when items can be inserted, reordered, or filtered.
- Engineers MUST specify an explicit, deterministic `estimateSize` callback that closely matches the median unrendered node height to prevent scrollbar jumping and excessive layout repositioning passes.
- Engineers MUST wrap scrollable elements with strict CSS containment (`contain: strict` or `contain: content; contain-intrinsic-size: ...`) to isolate layout and paint calculations from the parent document tree.
- Components NEVER trigger synchronous React state updates inside dynamic measurement listeners; dynamic size changes must be captured solely through TanStack Virtual's internal resize observer cycle.
- Engineers MUST pass a static ref to `getScrollElement` rather than dynamic element getters that re-evaluate or return null across render passes.
- Engineers MUST explicitly set `overscan` to a bounded, production-safe constant (typically between 3 and 10); unbounded or excessively large overscan counts (>25) are strictly prohibited in massive datasets to avoid DOM saturation.

## Bad vs Good Implementations
### Dynamic Height Row Virtualization with Hardware Acceleration and Containment

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Using marginTop forces synchronous layout reflow on every scroll frame. Overscan of 100 saturates the DOM. Using virtualItem.index as React key causes incorrect DOM reuse on filtering or reordering. The estimateSize is far too low, causing erratic scroll behavior, and measureElement is completely missing for dynamic items.
```typescript
import React from 'react';
import { useVirtualizer } from '@tanstack/react-virtual';

interface RowData { id: string; text: string; }

export const BadVirtualizedTable = ({ rows }: { rows: RowData[] }) => {
  const parentRef = React.useRef<HTMLDivElement>(null);
  const virtualizer = useVirtualizer({
    count: rows.length,
    getScrollElement: () => parentRef.current,
    estimateSize: () => 10, // Unrealistic size causes massive jump on scroll
    overscan: 100, // Anti-pattern: DOM saturation with 100+ unrendered items
  });

  return (
    <div ref={parentRef} style={{ height: '600px', overflowY: 'auto' }}>
      <div style={{ height: `${virtualizer.getTotalSize()}px`, position: 'relative' }}>
        {virtualizer.getVirtualItems().map((virtualItem) => (
          <div
            key={virtualItem.index} // Anti-pattern: index key breaks on dynamic mutation
            style={{
              position: 'absolute',
              top: 0,
              left: 0,
              width: '100%',
              marginTop: `${virtualItem.start}px`, // Anti-pattern: forces CPU reflow/layout
            }}
          >
            <div>{rows[virtualItem.index]?.text}</div>
          </div>
        ))}
      </div>
    </div>
  );
};
```

#### Production Standard (Correct)
> **Standard**: Implements GPU-accelerated transform positioning (`translateY`), isolates repaint cycles via `contain: strict`, binds dynamic sizing through `virtualizer.measureElement` with a `data-index` attribute, provides stable ID keys via `getItemKey`, and constrains overscan to 5 to avoid DOM node saturation.
```typescript
import React from 'react';
import { useVirtualizer } from '@tanstack/react-virtual';

interface RowData { id: string; text: string; }

const ESTIMATED_ROW_HEIGHT = 48;

export const GoodVirtualizedTable = ({ rows }: { rows: RowData[] }) => {
  const parentRef = React.useRef<HTMLDivElement>(null);

  const virtualizer = useVirtualizer({
    count: rows.length,
    getScrollElement: () => parentRef.current,
    estimateSize: () => ESTIMATED_ROW_HEIGHT,
    getItemKey: (index) => rows[index]?.id ?? index,
    overscan: 5,
  });

  return (
    <div
      ref={parentRef}
      style={{
        height: '600px',
        overflowY: 'auto',
        contain: 'strict',
      }}
    >
      <div
        style={{
          height: `${virtualizer.getTotalSize()}px`,
          width: '100%',
          position: 'relative',
        }}
      >
        {virtualizer.getVirtualItems().map((virtualItem) => {
          const row = rows[virtualItem.index];
          if (!row) return null;
          return (
            <div
              key={virtualItem.key}
              ref={virtualizer.measureElement}
              data-index={virtualItem.index}
              style={{
                position: 'absolute',
                top: 0,
                left: 0,
                width: '100%',
                transform: `translateY(${virtualItem.start}px)`,
                willChange: 'transform',
              }}
            >
              <div style={{ padding: '8px 16px', borderBottom: '1px solid #e5e7eb' }}>
                {row.text}
              </div>
            </div>
          );
        })}
      </div>
    </div>
  );
};
```
Recommended MCP Servers (mcp-serverlist.com)

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

Chrome DevTools MCP
Inspects layout recalculation frequency, frame drops, and DOM node counts under continuous scrolling workloads.
Recommended Agent Skills (askills.dev)

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

Lighthouse CI
Audits DOM size and layout stability metrics (CLS) to detect virtualization breakdowns and unbounded DOM node saturation.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: TanStack Virtual 3.0 Dynamic Measurement, Scroll Containment, and DOM Saturation Guardrails

TanStack Virtual 3.0 Dynamic Measurement, Scroll Containment, and DOM Saturation Guardrails defines an industrial-grade behavioral standard for frontend engineering. Enforces strict performance invariants for TanStack Virtual 3.0 in high-density tables and lists. Prevents layout thrashing, DOM node saturation, and measurement jitter by requiring continuous measurement containment, transform-based positioning, and explicit scroll margin offsets. Mandates non-reactive scroll containers, stable item keys, and proper teardown of resize observers. 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: Uncontained Dynamic Layout Thrashing and Render-Time Item Measurement 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 DriftUncontained Dynamic Layout Thrashing and Render-Time Item Measurement 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 attach the element measurement ref via `measureElement` callback directly to the rendered virtual row DOM node, never to child wrapper nodes or fragmented containers.

Engineers MUST ALWAYS attach the element measurement ref via `measureElement` callback directly to the rendered virtual row DOM node, never to child wrapper nodes or fragmented containers.

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 NEVER use `top` or `margin-top` for virtual item positioning

Engineers MUST NEVER use `top` or `margin-top` for virtual item positioning; all positioning MUST use GPU-accelerated CSS `transform: translateY(...)` combined with `will-change: transform` or native absolute layout without triggering document reflow.

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

Components MUST ALWAYS provide a stable, unique key to each virtual item matching `virtualItem.key` derived from data identity, NEVER relying on `virtualItem.index` when items can be inserted, reordered, or filtered.

Components MUST ALWAYS provide a stable, unique key to each virtual item matching `virtualItem.key` derived from data identity, NEVER relying on `virtualItem.index` when items can be inserted, reordered, or filtered.

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

Engineers MUST specify an explicit, deterministic `estimateSize` callback that closely matches the median unrendered node height to prevent scrollbar jumping and excessive layout repositioning passes.

Engineers MUST specify an explicit, deterministic `estimateSize` callback that closely matches the median unrendered node height to prevent scrollbar jumping and excessive layout repositioning passes.

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

Engineers MUST wrap scrollable elements with strict CSS containment (`contain

Engineers MUST wrap scrollable elements with strict CSS containment (`contain: strict` or `contain: content; contain-intrinsic-size: ...`) to isolate layout and paint calculations from the parent document tree.

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 trigger synchronous React state updates inside dynamic measurement listeners

Components NEVER trigger synchronous React state updates inside dynamic measurement listeners; dynamic size changes must be captured solely through TanStack Virtual's internal resize observer cycle.

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.
7

Engineers MUST pass a static ref to `getScrollElement` rather than dynamic element getters that re-evaluate or return null across render passes.

Engineers MUST pass a static ref to `getScrollElement` rather than dynamic element getters that re-evaluate or return null across render passes.

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.
8

Engineers MUST explicitly set `overscan` to a bounded, production-safe constant (typically between 3 and 10)

Engineers MUST explicitly set `overscan` to a bounded, production-safe constant (typically between 3 and 10); unbounded or excessively large overscan counts (>25) are strictly prohibited in massive datasets to avoid DOM saturation.

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 TanStack Virtual 3.0 Dynamic Measurement, Scroll Containment, and DOM Saturation Guardrails critical for AI coding assistants?

Enforces strict performance invariants for TanStack Virtual 3.0 in high-density tables and lists. Prevents layout thrashing, DOM node saturation, and measurement jitter by requiring continuous measurement containment, transform-based positioning, and explicit scroll margin offsets. Mandates non-reactive scroll containers, stable item keys, and proper teardown of resize observers. 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 (Uncontained Dynamic Layout Thrashing and Render-Time Item Measurement 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

TanStack