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-dynamic-measurement-saturation-guardrail

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

Enforces strict industrial standards for TanStack Virtual 3.0 in massive datasets and dynamic tables. Mandates native ref-based element measurement via measureElement, strict containment of scroll margins to prevent viewport jitter, and hard limits on overscan to avoid catastrophic DOM node saturation.

Prohibited Anti-Pattern: Unbounded Overscan, Manual getBoundingClientRect Layout Thrashing, and Index-Keyed Dynamic Rows

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 Guardrail - Enforces strict industrial standards for TanStack Virtual 3.0 in massive datasets and dynamic tables. Mandates native ref-based element measurement via measureElement, strict containment of scroll margins to prevent viewport jitter, and hard limits on overscan to avoid catastrophic DOM node saturation.
globs: src/**/*.{ts,tsx}, app/**/*.{ts,tsx}, components/**/*.{ts,tsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/tanstack-virtual-dynamic-measurement-saturation-guardrail"
---

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

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unbounded Overscan, Manual getBoundingClientRect Layout Thrashing, and Index-Keyed Dynamic Rows

## System Constraints
You are a Principal Software Architect enforcing production invariants for TanStack Virtual 3.0 windowing. You must prevent memory leaks, layout thrashing, incorrect dynamic measurement, and DOM node saturation in virtualized tables and lists. Enforce stable keys, automatic ref measurement via measureElement, bounded overscan, and absolute positioning transforms.

## Strict Guidelines
- Engineers MUST ALWAYS attach `ref={virtualizer.measureElement}` accompanied by `data-index={virtualRow.index}` on dynamically measured elements to trigger measurement inside resize observers rather than manual layout passes.
- Engineers MUST NOT invoke `getBoundingClientRect()`, `offsetHeight`, or trigger manual DOM measuring inside `useEffect` or render loops.
- Components MUST ALWAYS use unique, stable business entity identifiers (e.g., `key={row.id}`) for virtualized item containers instead of `virtualRow.index` or `virtualRow.key` alone to prevent DOM recycling state corruption.
- Engineers MUST constrain `overscan` to a strictly bounded range (recommended: 3 to 8 items). Engineers MUST NOT set excessive overscan (> 15 items in tables) to prevent DOM node saturation and frame drops.
- Components MUST calculate offsets using CSS GPU-accelerated transforms (`transform: translateY(${virtualRow.start}px)`) with `position: absolute; top: 0; left: 0; width: 100%;` rather than `top` or margin-based positioning.
- When a virtualizer is nested inside containers with sticky headers or external offsets, engineers MUST configure `scrollMargin` in `useVirtualizer` options and sync it to the container's layout offset.
- Virtual container elements MUST specify `contain: 'strict'` or `contain: 'size layout paint'` and `will-change: transform` to isolate browser recalculations from the parent DOM tree.

## Bad vs Good Implementations
### Dynamic Height Row Virtualization with TanStack Virtual 3.0

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The bad example violates DOM saturation guardrails with an overscan of 50, positions elements via 'top' instead of hardware-accelerated transforms, omits dynamic measurement registration leading to clipping, and keys by array index causing DOM node state misalignment during scroll.
```typescript
import React, { useRef, useEffect } from 'react';
import { useVirtualizer } from '@tanstack/react-virtual';

interface Item {
  id: string;
  content: string;
}

export const BadVirtualizedList = ({ items }: { items: Item[] }) => {
  const parentRef = useRef<HTMLDivElement>(null);

  const virtualizer = useVirtualizer({
    count: items.length,
    getScrollElement: () => parentRef.current,
    estimateSize: () => 50,
    overscan: 50, // CRITICAL: Unbounded overscan saturates DOM nodes
  });

  return (
    <div ref={parentRef} style={{ height: '600px', overflowY: 'auto' }}>
      <div style={{ height: `${virtualizer.getTotalSize()}px`, position: 'relative' }}>
        {virtualizer.getVirtualItems().map((virtualRow) => {
          const item = items[virtualRow.index];
          // CRITICAL: Manual layout thrashing via getBoundingClientRect inside render/effect
          // CRITICAL: Keying by virtualRow.index causes DOM recycling bugs
          return (
            <div
              key={virtualRow.index}
              style={{
                position: 'absolute',
                top: `${virtualRow.start}px`,
                left: 0,
                width: '100%'
              }}
            >
              <p>{item.content}</p>
            </div>
          );
        })}
      </div>
    </div>
  );
};
```

#### Production Standard (Correct)
> **Standard**: The good example sets a strictly bounded overscan of 5, links dynamic row heights via measureElement and data-index attributes, handles scrollMargin offsets, positions nodes using translateY with willChange for GPU composite layers, and uses contain: 'strict' to isolate browser layout passes.
```typescript
import React, { useRef } from 'react';
import { useVirtualizer } from '@tanstack/react-virtual';

interface Item {
  id: string;
  content: string;
}

interface GoodVirtualizedListProps {
  items: Item[];
  scrollMarginOffset?: number;
}

export const GoodVirtualizedList: React.FC<GoodVirtualizedListProps> = ({
  items,
  scrollMarginOffset = 0,
}) => {
  const parentRef = useRef<HTMLDivElement>(null);

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

  return (
    <div
      ref={parentRef}
      style={{
        height: '600px',
        overflowY: 'auto',
        contain: 'strict',
      }}
    >
      <div
        style={{
          height: `${virtualizer.getTotalSize()}px`,
          width: '100%',
          position: 'relative',
        }}
      >
        {virtualizer.getVirtualItems().map((virtualRow) => {
          const item = items[virtualRow.index];
          if (!item) return null;

          return (
            <div
              key={virtualRow.key}
              ref={virtualizer.measureElement}
              data-index={virtualRow.index}
              style={{
                position: 'absolute',
                top: 0,
                left: 0,
                width: '100%',
                transform: `translateY(${virtualRow.start - virtualizer.options.scrollMargin}px)`,
                willChange: 'transform',
              }}
            >
              <div style={{ padding: '12px 16px', borderBottom: '1px solid #e2e8f0' }}>
                <p style={{ margin: 0, wordBreak: 'break-word' }}>{item.content}</p>
              </div>
            </div>
          );
        })}
      </div>
    </div>
  );
};
```
Recommended MCP Servers (mcp-serverlist.com)

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

Chrome DevTools MCP
Automated performance trace collection, layout shift metrics, and DOM tree inspection under scrolling conditions.
Recommended Agent Skills (askills.dev)

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

Frontend Performance Audit Skill
Evaluates virtualized list implementations for layout thrashing, DOM saturation, and frame drops.
Architectural Specification & Invariant Rationale

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

TanStack Virtual 3.0 Dynamic Measurement, Scroll Containment, and DOM Saturation Guardrail defines an industrial-grade behavioral standard for frontend engineering. Enforces strict industrial standards for TanStack Virtual 3.0 in massive datasets and dynamic tables. Mandates native ref-based element measurement via measureElement, strict containment of scroll margins to prevent viewport jitter, and hard limits on overscan to avoid catastrophic DOM node saturation. 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: Unbounded Overscan, Manual getBoundingClientRect Layout Thrashing, and Index-Keyed Dynamic Rows 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 DriftUnbounded Overscan, Manual getBoundingClientRect Layout Thrashing, and Index-Keyed Dynamic RowsCritical
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 `ref={virtualizer.measureElement}` accompanied by `data-index={virtualRow.index}` on dynamically measured elements to trigger measurement inside resize observers rather than manual layout passes.

Engineers MUST ALWAYS attach `ref={virtualizer.measureElement}` accompanied by `data-index={virtualRow.index}` on dynamically measured elements to trigger measurement inside resize observers rather than manual layout 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.
2

Engineers MUST NOT invoke `getBoundingClientRect()`, `offsetHeight`, or trigger manual DOM measuring inside `useEffect` or render loops.

Engineers MUST NOT invoke `getBoundingClientRect()`, `offsetHeight`, or trigger manual DOM measuring inside `useEffect` or render loops.

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 use unique, stable business entity identifiers (e.g., `key={row.id}`) for virtualized item containers instead of `virtualRow.index` or `virtualRow.key` alone to prevent DOM recycling state corruption.

Components MUST ALWAYS use unique, stable business entity identifiers (e.g., `key={row.id}`) for virtualized item containers instead of `virtualRow.index` or `virtualRow.key` alone to prevent DOM recycling state corruption.

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 constrain `overscan` to a strictly bounded range (recommended

Engineers MUST constrain `overscan` to a strictly bounded range (recommended: 3 to 8 items). Engineers MUST NOT set excessive overscan (> 15 items in tables) to prevent DOM node saturation and frame drops.

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 MUST calculate offsets using CSS GPU-accelerated transforms (`transform

Components MUST calculate offsets using CSS GPU-accelerated transforms (`transform: translateY(${virtualRow.start}px)`) with `position: absolute; top: 0; left: 0; width: 100%;` rather than `top` or margin-based positioning.

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

When a virtualizer is nested inside containers with sticky headers or external offsets, engineers MUST configure `scrollMargin` in `useVirtualizer` options and sync it to the container's layout offset.

When a virtualizer is nested inside containers with sticky headers or external offsets, engineers MUST configure `scrollMargin` in `useVirtualizer` options and sync it to the container's layout offset.

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

Virtual container elements MUST specify `contain

Virtual container elements MUST specify `contain: 'strict'` or `contain: 'size layout paint'` and `will-change: transform` to isolate browser recalculations from the parent DOM 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.
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 Guardrail critical for AI coding assistants?

Enforces strict industrial standards for TanStack Virtual 3.0 in massive datasets and dynamic tables. Mandates native ref-based element measurement via measureElement, strict containment of scroll margins to prevent viewport jitter, and hard limits on overscan to avoid catastrophic DOM node saturation. 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 (Unbounded Overscan, Manual getBoundingClientRect Layout Thrashing, and Index-Keyed Dynamic Rows) 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