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-v3-windowing-performance-production-standard

TanStack Virtual 3.0 Dynamic Windowing & Layout Containment Invariant

Enforces strict DOM node containment, GPU-accelerated absolute transforms, and robust dynamic height measurement mechanics in TanStack Virtual 3.0. Prevents layout thrashing, scrollbar jitter, and memory saturation in high-throughput enterprise data grids by mandating hardware-accelerated transforms, data-index hooks, and bounded overscan constraints.

Prohibited Anti-Pattern: Uncontained Layout Reflows, Jittery Measurements, and Excessive Overscan in Virtualized Tables

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: TanStack Virtual 3.0 Dynamic Windowing & Layout Containment Invariant - Enforces strict DOM node containment, GPU-accelerated absolute transforms, and robust dynamic height measurement mechanics in TanStack Virtual 3.0. Prevents layout thrashing, scrollbar jitter, and memory saturation in high-throughput enterprise data grids by mandating hardware-accelerated transforms, data-index hooks, and bounded overscan constraints.
globs: src/**/*.{ts,tsx}, components/**/*.{ts,tsx}, features/**/*.{ts,tsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/tanstack-virtual-v3-windowing-performance-production-standard"
---

# TanStack Virtual 3.0 Dynamic Windowing & Layout Containment Invariant

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Uncontained Layout Reflows, Jittery Measurements, and Excessive Overscan in Virtualized Tables

## System Constraints
You are a Principal Frontend Architect enforcing TanStack Virtual 3.0 windowing standards. You must ensure all virtualized collections prevent layout thrashing, maintain stable dynamic measurements, and eliminate DOM node saturation. Reject raw top positioning, missing dynamic measurement attributes, volatile array index keys, unbounded overscan, and unconstrained scroll containers.

## Strict Guidelines
- Engineers MUST ALWAYS use `transform: translateY(${virtualRow.start}px)` (or translateX) rather than `top`/`left` to maintain composite-only rendering layers.
- Engineers MUST ALWAYS attach `ref={virtualizer.measureElement}` and provide the `data-index={virtualRow.index}` attribute on every dynamically measured virtual element.
- Engineers MUST ALWAYS use stable entity IDs or `virtualRow.key` for item keys, NEVER raw array loop indices which corrupt node reuse.
- Engineers MUST bound `overscan` between 2 and 8 nodes for high-density tables; unbounded or double-digit overscan values (> 15) are strictly prohibited.
- Components MUST apply CSS layout containment (`contain: strict` or `contain: layout size`) on outer scroll viewports and inner stretch track wrappers (`totalSize`).
- Services and hooks MUST configure explicit `scrollMargin` when headers, toolbars, or footers reside inside the scroll element to prevent offset calculation drift and scroll jitter.

## Bad vs Good Implementations
### Dynamic Element Virtualization with Stable Measurement and GPU Composition

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Using 'top' forces costly layout recalculations on every scroll event instead of GPU compositing. An overscan of 50 causes DOM node saturation. Using loop index as key destroys reconciliation during updates, and omitting 'ref={virtualizer.measureElement}' with 'data-index' breaks dynamic sizing calculations, resulting in overlapping items and severe scrollbar jumping.
```typescript
import React, { useRef } from 'react';
import { useVirtualizer } from '@tanstack/react-virtual';

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

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

  // BAD: Excessive overscan, no dynamic measurement hook, naive estimate
  const virtualizer = useVirtualizer({
    count: items.length,
    getScrollElement: () => parentRef.current,
    estimateSize: () => 35,
    overscan: 50,
  });

  return (
    <div ref={parentRef} style={{ height: '600px', overflowY: 'auto' }}>
      <div style={{ height: `${virtualizer.getTotalSize()}px`, position: 'relative' }}>
        {virtualizer.getVirtualItems().map((virtualRow, idx) => (
          // BAD: Using loop index as key, 'top' styling causes heavy reflows,
          // missing data-index and ref for dynamic content measurement
          <div
            key={idx}
            style={{
              position: 'absolute',
              top: `${virtualRow.start}px`,
              left: 0,
              width: '100%',
            }}
          >
            {items[virtualRow.index].content}
          </div>
        ))}
      </div>
    </div>
  );
};
```

#### Production Standard (Correct)
> **Standard**: Applies GPU-accelerated 'transform: translateY' to isolate changes to composite layers. Sets 'contain: strict' on the scrolling viewport to prevent subtree recalculation leaks. Dynamically measures items accurately using 'ref={virtualizer.measureElement}' and 'data-index', using a balanced overscan (5) and 'virtualRow.key' to guarantee persistent identity and smooth 60fps scrolling.
```typescript
import React, { useRef } from 'react';
import { useVirtualizer } from '@tanstack/react-virtual';

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

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

  const virtualizer = useVirtualizer({
    count: items.length,
    getScrollElement: () => parentRef.current,
    estimateSize: () => 48,
    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((virtualRow) => {
          const item = items[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',
              }}
            >
              {item.content}
            </div>
          );
        })}
      </div>
    </div>
  );
};
```
Recommended MCP Servers (mcp-serverlist.com)

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

Chrome DevTools MCP
Instruments live DOM node counts, layout shift (CLS), and paint/composite timings during rapid virtualization scrolling.
Recommended Agent Skills (askills.dev)

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

Lighthouse CI
Automated performance audits validating DOM size limits (< 1,400 total nodes) and cumulative layout stability.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: TanStack Virtual 3.0 Dynamic Windowing & Layout Containment Invariant

TanStack Virtual 3.0 Dynamic Windowing & Layout Containment Invariant defines an industrial-grade behavioral standard for frontend engineering. Enforces strict DOM node containment, GPU-accelerated absolute transforms, and robust dynamic height measurement mechanics in TanStack Virtual 3.0. Prevents layout thrashing, scrollbar jitter, and memory saturation in high-throughput enterprise data grids by mandating hardware-accelerated transforms, data-index hooks, and bounded overscan constraints. 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 Layout Reflows, Jittery Measurements, and Excessive Overscan in Virtualized Tables 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 Layout Reflows, Jittery Measurements, and Excessive Overscan in Virtualized TablesCritical
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 use `transform

Engineers MUST ALWAYS use `transform: translateY(${virtualRow.start}px)` (or translateX) rather than `top`/`left` to maintain composite-only rendering layers.

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 attach `ref={virtualizer.measureElement}` and provide the `data-index={virtualRow.index}` attribute on every dynamically measured virtual element.

Engineers MUST ALWAYS attach `ref={virtualizer.measureElement}` and provide the `data-index={virtualRow.index}` attribute on every dynamically measured virtual element.

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 ALWAYS use stable entity IDs or `virtualRow.key` for item keys, NEVER raw array loop indices which corrupt node reuse.

Engineers MUST ALWAYS use stable entity IDs or `virtualRow.key` for item keys, NEVER raw array loop indices which corrupt node reuse.

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 bound `overscan` between 2 and 8 nodes for high-density tables

Engineers MUST bound `overscan` between 2 and 8 nodes for high-density tables; unbounded or double-digit overscan values (> 15) are strictly prohibited.

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 apply CSS layout containment (`contain

Components MUST apply CSS layout containment (`contain: strict` or `contain: layout size`) on outer scroll viewports and inner stretch track wrappers (`totalSize`).

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

Services and hooks MUST configure explicit `scrollMargin` when headers, toolbars, or footers reside inside the scroll element to prevent offset calculation drift and scroll jitter.

Services and hooks MUST configure explicit `scrollMargin` when headers, toolbars, or footers reside inside the scroll element to prevent offset calculation drift and scroll jitter.

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 & Layout Containment Invariant critical for AI coding assistants?

Enforces strict DOM node containment, GPU-accelerated absolute transforms, and robust dynamic height measurement mechanics in TanStack Virtual 3.0. Prevents layout thrashing, scrollbar jitter, and memory saturation in high-throughput enterprise data grids by mandating hardware-accelerated transforms, data-index hooks, and bounded overscan constraints. 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 Layout Reflows, Jittery Measurements, and Excessive Overscan in Virtualized Tables) 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