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

TanStack Virtual 3.0 Dynamic Windowing & Node Containment Standard

Mandates deterministic dynamic element measurement, hardware-accelerated transforms, and bounded overscan configurations in TanStack Virtual 3.0. Enforces strict containment of scrollable bounds and explicit node measuring via data-index to eliminate DOM node saturation, layout thrashing, and scroll jitter in high-density tables.

Prohibited Anti-Pattern: Unbounded Overscan and Dynamic Sizing Without Node Measurement Containment Causing Forced Reflows

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: TanStack Virtual 3.0 Dynamic Windowing & Node Containment Standard - Mandates deterministic dynamic element measurement, hardware-accelerated transforms, and bounded overscan configurations in TanStack Virtual 3.0. Enforces strict containment of scrollable bounds and explicit node measuring via data-index to eliminate DOM node saturation, layout thrashing, and scroll jitter in high-density tables.
globs: src/**/*.{ts,tsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/tanstack-virtual-dynamic-measurement-guardrail"
---

# TanStack Virtual 3.0 Dynamic Windowing & Node Containment Standard

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unbounded Overscan and Dynamic Sizing Without Node Measurement Containment Causing Forced Reflows

## System Constraints
You are a Principal Frontend Architect enforcing TanStack Virtual 3.0 production invariants. Mandate hardware-accelerated transforms, dynamic measurement containment via measureElement and data-index, strict overscan caps, and structural containment of scroll containers to prevent DOM bloat and scrollbar thrashing.

## Strict Guidelines
- Engineers MUST ALWAYS attach `ref={virtualizer.measureElement}` and provide `data-index={virtualRow.index}` on dynamically measured row/column elements.
- Engineers MUST ALWAYS use CSS `transform: translateY(...)` (or `translateX`) instead of mutating `top`, `bottom`, `left`, or `margin` to prevent layout reflows during virtualization updates.
- Engineers MUST configure `overscan` to a strictly bounded threshold (typically between 3 and 10), and MUST NOT exceed 15 in production table views to prevent DOM node saturation.
- Components MUST wrap virtualized elements inside a container whose height/width matches `virtualizer.getTotalSize()` with `position: 'relative'` and `width: '100%'`.
- Engineers MUST NOT trigger manual layout queries (`getBoundingClientRect`, `offsetHeight`, `clientHeight`) during rendering; all measurements MUST rely on TanStack Virtual's batched `ResizeObserver` lifecycle.
- Code MUST specify a deterministic `estimateSize` callback returning a baseline close to median row height to avoid catastrophic scrollbar jitter and cumulative layout shifts (CLS).
- Components NEVER attach non-memoized or inline anonymous functions to the `count`, `getScrollElement`, or `estimateSize` options inside `useVirtualizer` when it causes unnecessary instance recreation.

## Bad vs Good Implementations
### Dynamic Table Row Virtualization with Hardware Acceleration and Measurement

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Using top mutations causes continuous layout recalculations on every scroll tick. Overscan is set to 100, which negates virtualization benefits by saturating the DOM. Dynamic elements are never measured with measureElement or data-index, causing overlapping content when row heights vary.
```typescript
import React, { useRef } from 'react';
import { useVirtualizer } from '@tanstack/react-virtual';

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

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

  // ANTI-PATTERN: Excessive overscan, inline estimate, and missing dynamic ref attachment
  const virtualizer = useVirtualizer({
    count: rows.length,
    getScrollElement: () => parentRef.current,
    estimateSize: () => 35, // Static estimate for dynamic content
    overscan: 100 // DOM saturation: renders hundreds of nodes offscreen
  });

  return (
    <div ref={parentRef} style={{ height: '500px', overflowY: 'auto' }}>
      <div style={{ height: `${virtualizer.getTotalSize()}px` }}>
        {virtualizer.getVirtualItems().map((virtualRow) => (
          <div
            key={virtualRow.key}
            // ANTI-PATTERN: Mutating 'top' causes reflows; missing measureElement and data-index
            style={{
              position: 'absolute',
              top: `${virtualRow.start}px`,
              left: 0,
              width: '100%'
            }}
          >
            {rows[virtualRow.index].content}
          </div>
        ))}
      </div>
    </div>
  );
};
```

#### Production Standard (Correct)
> **Standard**: Adheres to performance invariants: overscan is capped at 5 to prevent DOM saturation, hardware-accelerated transforms (`translateY`) eliminate reflows, dynamic content is properly measured via `measureElement` paired with `data-index`, and CSS containment (`contain: strict`) bounds layout recalculations to the scroll container.
```typescript
import React, { useRef, useCallback } from 'react';
import { useVirtualizer } from '@tanstack/react-virtual';

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

const ESTIMATED_ROW_HEIGHT = 48;
const PRODUCTION_OVERSCAN = 5;

export const OptimizedVirtualTable = ({ rows }: { rows: RowData[] }) => {
  const parentRef = useRef<HTMLDivElement>(null);
  const getScrollElement = useCallback(() => parentRef.current, []);
  const estimateSize = useCallback(() => ESTIMATED_ROW_HEIGHT, []);

  const virtualizer = useVirtualizer({
    count: rows.length,
    getScrollElement,
    estimateSize,
    overscan: PRODUCTION_OVERSCAN
  });

  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 row = rows[virtualRow.index];
          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}px)`,
                willChange: 'transform'
              }}
            >
              <div style={{ padding: '12px 16px', borderBottom: '1px solid #e5e7eb' }}>
                {row.content}
              </div>
            </div>
          );
        })}
      </div>
    </div>
  );
};
```
Recommended MCP Servers (mcp-serverlist.com)

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

Puppeteer Performance Evaluator
Validates DOM node counts, cumulative layout shifts, and rendering frame rates under simulated scroll load.
Recommended Agent Skills (askills.dev)

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

React Virtual Profiler
Profiles TanStack Virtual dynamic item measurement times, resize observer invocations, and layout containment.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: TanStack Virtual 3.0 Dynamic Windowing & Node Containment Standard

TanStack Virtual 3.0 Dynamic Windowing & Node Containment Standard defines an industrial-grade behavioral standard for frontend engineering. Mandates deterministic dynamic element measurement, hardware-accelerated transforms, and bounded overscan configurations in TanStack Virtual 3.0. Enforces strict containment of scrollable bounds and explicit node measuring via data-index to eliminate DOM node saturation, layout thrashing, and scroll jitter in high-density tables. 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 and Dynamic Sizing Without Node Measurement Containment Causing Forced Reflows 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 and Dynamic Sizing Without Node Measurement Containment Causing Forced ReflowsCritical
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}` and provide `data-index={virtualRow.index}` on dynamically measured row/column elements.

Engineers MUST ALWAYS attach `ref={virtualizer.measureElement}` and provide `data-index={virtualRow.index}` on dynamically measured row/column elements.

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 ALWAYS use CSS `transform

Engineers MUST ALWAYS use CSS `transform: translateY(...)` (or `translateX`) instead of mutating `top`, `bottom`, `left`, or `margin` to prevent layout reflows during virtualization updates.

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

Engineers MUST configure `overscan` to a strictly bounded threshold (typically between 3 and 10), and MUST NOT exceed 15 in production table views to prevent DOM node saturation.

Engineers MUST configure `overscan` to a strictly bounded threshold (typically between 3 and 10), and MUST NOT exceed 15 in production table views to prevent DOM node 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.
4

Components MUST wrap virtualized elements inside a container whose height/width matches `virtualizer.getTotalSize()` with `position

Components MUST wrap virtualized elements inside a container whose height/width matches `virtualizer.getTotalSize()` with `position: 'relative'` and `width: '100%'`.

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 NOT trigger manual layout queries (`getBoundingClientRect`, `offsetHeight`, `clientHeight`) during rendering

Engineers MUST NOT trigger manual layout queries (`getBoundingClientRect`, `offsetHeight`, `clientHeight`) during rendering; all measurements MUST rely on TanStack Virtual's batched `ResizeObserver` lifecycle.

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

Code MUST specify a deterministic `estimateSize` callback returning a baseline close to median row height to avoid catastrophic scrollbar jitter and cumulative layout shifts (CLS).

Code MUST specify a deterministic `estimateSize` callback returning a baseline close to median row height to avoid catastrophic scrollbar jitter and cumulative layout shifts (CLS).

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

Components NEVER attach non-memoized or inline anonymous functions to the `count`, `getScrollElement`, or `estimateSize` options inside `useVirtualizer` when it causes unnecessary instance recreation.

Components NEVER attach non-memoized or inline anonymous functions to the `count`, `getScrollElement`, or `estimateSize` options inside `useVirtualizer` when it causes unnecessary instance recreation.

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 Windowing & Node Containment Standard critical for AI coding assistants?

Mandates deterministic dynamic element measurement, hardware-accelerated transforms, and bounded overscan configurations in TanStack Virtual 3.0. Enforces strict containment of scrollable bounds and explicit node measuring via data-index to eliminate DOM node saturation, layout thrashing, and scroll jitter in high-density tables. 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 and Dynamic Sizing Without Node Measurement Containment Causing Forced Reflows) 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