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: react-19-resource-preload-dedup-invariant

React 19 Document Resource Preload Priority & Deduplication Invariant

Enforces deterministic asset preloading and deduplication via React 19's native resource dispatchers and hoisted metadata elements. Eliminates client-side waterfalls, DOM mutation side-effects, and duplicate script execution by integrating directly with React's streaming resource discovery engine.

Prohibited Anti-Pattern: Imperative Head Injections and Client-Side useEffect Preloading Waterfall

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: React 19 Document Resource Preload Priority & Deduplication Invariant - Enforces deterministic asset preloading and deduplication via React 19's native resource dispatchers and hoisted metadata elements. Eliminates client-side waterfalls, DOM mutation side-effects, and duplicate script execution by integrating directly with React's streaming resource discovery engine.
globs: src/**/*.{ts,tsx}, app/**/*.{ts,tsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/react-19-resource-preload-dedup-invariant"
---

# React 19 Document Resource Preload Priority & Deduplication Invariant

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Imperative Head Injections and Client-Side useEffect Preloading Waterfall

## System Constraints
You are a Principal Engineer enforcing React 19 Document Resource Preload Priority & Deduplication Invariant. Mandate invariants that eliminate client waterfalls and race conditions by transitioning legacy DOM element injection to React 19 native resource preloading APIs (`preload`, `preinit`, `preloadModule`, `preinitModule`) and hoisted link/script tags with explicit `precedence` attributes.

## Strict Guidelines
- Engineers MUST ALWAYS use `react-dom` functions (`preload`, `preinit`, `preloadModule`, `preinitModule`) or native hoisted tags (`<link rel="stylesheet" precedence="..." />`) for document resource loading.
- Engineers MUST NOT imperatively mutate `document.head` or `document.body` via `document.createElement('script')` or `document.createElement('link')` inside lifecycle hooks.
- Code MUST NOT invoke resource preloading inside `useEffect` or `useLayoutEffect`, as it defers discovery until post-hydration and creates client-side waterfalls.
- Components rendering `<link rel="stylesheet">` MUST specify an explicit `precedence` attribute (`precedence="default"`, `"high"`, `"reset"`) to enable React 19's internal style sheet hoisting and cascade deduplication.
- Engineers MUST declare `crossOrigin` attributes consistently between `preload` calls and subsequent consumption to avoid dual-fetch network duplication.
- Resource hints for third-party origins MUST use `preconnect` or `dns-prefetch` via `react-dom`'s `preconnect` helper during the render phase.

## Bad vs Good Implementations
### Imperative Head Injection vs. React 19 Native Hoisting and Preloading

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Using useEffect causes a client-side execution waterfall, completely invisible to server-side streaming discovery. Manual head injection bypasses React 19's built-in deduplication and style precedence ordering, risking duplicate script execution and broken cascade rules.
```typescript
import { useEffect } from 'react';

interface AnalyticsWidgetProps {
  scriptUrl: string;
  styleUrl: string;
}

export function AnalyticsWidget({ scriptUrl, styleUrl }: AnalyticsWidgetProps) {
  // ANTI-PATTERN: Client-side waterfall; DOM mutation bypasses React 19 streaming scheduler
  useEffect(() => {
    const existingScript = document.querySelector(`script[src="${scriptUrl}"]`);
    if (!existingScript) {
      const script = document.createElement('script');
      script.src = scriptUrl;
      script.async = true;
      document.head.appendChild(script);
    }

    const link = document.createElement('link');
    link.rel = 'stylesheet';
    link.href = styleUrl;
    document.head.appendChild(link);
  }, [scriptUrl, styleUrl]);

  return <div id="analytics-widget-container" />;
}
```

#### Production Standard (Correct)
> **Standard**: Calls `preload` and `preinit` during render so React emits resource hints into the streaming HTML stream before rendering completes. Declaring `precedence="high"` triggers native React 19 stylesheet hoisting and deduplication, ensuring predictable CSS cascade without runtime side-effects.
```typescript
import { preload, preinit } from 'react-dom';

interface AnalyticsWidgetProps {
  scriptUrl: string;
  styleUrl: string;
  fontUrl: string;
}

export function AnalyticsWidget({ scriptUrl, styleUrl, fontUrl }: AnalyticsWidgetProps) {
  // Invariant: Preload critical secondary assets as early as the render phase
  preload(fontUrl, { as: 'font', type: 'font/woff2', crossOrigin: 'anonymous' });

  // Invariant: Native preinit discovers and executes external script with auto-deduplication
  preinit(scriptUrl, { as: 'script' });

  return (
    <>
      {/* React 19 hoists this to <head> and deduplicates across identical hrefs */}
      <link rel="stylesheet" href={styleUrl} precedence="high" />
      <div id="analytics-widget-container" />
    </>
  );
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Lighthouse Audit Provider
MCP endpoint for running Core Web Vitals checks and identifying resource loading waterfalls.
Recommended Agent Skills (askills.dev)

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

React 19 Compatibility Linter
Validates React 19 native DOM element extensions and warns on illegal imperative document mutations.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: React 19 Document Resource Preload Priority & Deduplication Invariant

React 19 Document Resource Preload Priority & Deduplication Invariant defines an industrial-grade behavioral standard for frontend engineering. Enforces deterministic asset preloading and deduplication via React 19's native resource dispatchers and hoisted metadata elements. Eliminates client-side waterfalls, DOM mutation side-effects, and duplicate script execution by integrating directly with React's streaming resource discovery engine. 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: Imperative Head Injections and Client-Side useEffect Preloading Waterfall 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 DriftImperative Head Injections and Client-Side useEffect Preloading WaterfallCritical
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 `react-dom` functions (`preload`, `preinit`, `preloadModule`, `preinitModule`) or native hoisted tags (`<link rel="stylesheet" precedence="..." />`) for document resource loading.

Engineers MUST ALWAYS use `react-dom` functions (`preload`, `preinit`, `preloadModule`, `preinitModule`) or native hoisted tags (`<link rel="stylesheet" precedence="..." />`) for document resource loading.

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 imperatively mutate `document.head` or `document.body` via `document.createElement('script')` or `document.createElement('link')` inside lifecycle hooks.

Engineers MUST NOT imperatively mutate `document.head` or `document.body` via `document.createElement('script')` or `document.createElement('link')` inside lifecycle hooks.

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

Code MUST NOT invoke resource preloading inside `useEffect` or `useLayoutEffect`, as it defers discovery until post-hydration and creates client-side waterfalls.

Code MUST NOT invoke resource preloading inside `useEffect` or `useLayoutEffect`, as it defers discovery until post-hydration and creates client-side waterfalls.

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 rendering `<link rel="stylesheet">` MUST specify an explicit `precedence` attribute (`precedence="default"`, `"high"`, `"reset"`) to enable React 19's internal style sheet hoisting and cascade deduplication.

Components rendering `<link rel="stylesheet">` MUST specify an explicit `precedence` attribute (`precedence="default"`, `"high"`, `"reset"`) to enable React 19's internal style sheet hoisting and cascade deduplication.

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 declare `crossOrigin` attributes consistently between `preload` calls and subsequent consumption to avoid dual-fetch network duplication.

Engineers MUST declare `crossOrigin` attributes consistently between `preload` calls and subsequent consumption to avoid dual-fetch network duplication.

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

Resource hints for third-party origins MUST use `preconnect` or `dns-prefetch` via `react-dom`'s `preconnect` helper during the render phase.

Resource hints for third-party origins MUST use `preconnect` or `dns-prefetch` via `react-dom`'s `preconnect` helper during the render phase.

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 React 19 Document Resource Preload Priority & Deduplication Invariant critical for AI coding assistants?

Enforces deterministic asset preloading and deduplication via React 19's native resource dispatchers and hoisted metadata elements. Eliminates client-side waterfalls, DOM mutation side-effects, and duplicate script execution by integrating directly with React's streaming resource discovery engine. 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 (Imperative Head Injections and Client-Side useEffect Preloading Waterfall) 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

React