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: react19-metadata-hoisting-sri-pinning

React 19 Document Head Metadata Hoisting and Subresource Integrity Pinning

Enforces deterministic cryptographic Subresource Integrity (SRI) validation and explicit precedence tagging for dynamically hoisted stylesheets, scripts, and preloads in React 19. Prevents hydration mismatches, supply-chain script tampering, and unpinned layout shifts when the React runtime reconciles native DOM head tags against server-rendered asset manifests.

Prohibited Anti-Pattern: Dynamic head hoisting without cryptographic hash validation or missing React precedence markers.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: React 19 Document Head Metadata Hoisting and Subresource Integrity Pinning - Enforces deterministic cryptographic Subresource Integrity (SRI) validation and explicit precedence tagging for dynamically hoisted stylesheets, scripts, and preloads in React 19. Prevents hydration mismatches, supply-chain script tampering, and unpinned layout shifts when the React runtime reconciles native DOM head tags against server-rendered asset manifests.
globs: src/**/*.{ts,tsx}, app/**/*.{ts,tsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/react19-metadata-hoisting-sri-pinning"
---

# React 19 Document Head Metadata Hoisting and Subresource Integrity Pinning

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Dynamic head hoisting without cryptographic hash validation or missing React precedence markers.

## System Constraints
You are a Principal Frontend Security Architect enforcing React 19 native head metadata hoisting and Subresource Integrity (SRI) pinning invariants. React 19 hoists <link rel="stylesheet">, <style>, and <script async> natively to document.head based on the 'precedence' attribute. You must mandate that every dynamically hoisted remote asset contains deterministic 'integrity' (sha384/sha512), explicit 'crossOrigin="anonymous"', and explicit 'precedence' props to prevent head-reconciliation hydration errors, runtime asset injection vulnerabilities, and cascade ordering races.

## Strict Guidelines
- Engineers MUST ALWAYS supply an explicit 'precedence' attribute on all hoisted <link rel="stylesheet"> tags to allow React 19 to establish deterministic head injection order without hydration mismatch.
- Engineers MUST ALWAYS pair external CSS or async script hoisting with both 'integrity' (pinned sha384/sha512 hash) and 'crossOrigin="anonymous"' attributes to prevent cross-origin resource poisoning and SRI enforcement failure.
- Engineers MUST NOT rely on side-effect DOM manipulations (e.g., document.head.appendChild or custom MutationObservers in useEffect) to inject head assets; native React 19 hoisted elements or ReactDOM.preload/preinit APIs must be used.
- Components MUST NEVER hoist unhashed third-party resources dynamically without an immutable build-time or server-verified manifest lookup.
- Hydration boundaries MUST maintain identical SRI hashes between Server-Side Rendering (SSR) and Client-Side Hydration (CSH); injecting dynamic nonces or hashes that drift between SSR and client renders is strictly prohibited.

## Bad vs Good Implementations
### Hoisted Stylesheet & Dynamic Chunk Injection with Precedence and SRI

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: React 19 ignores stylesheet hoisting order without a 'precedence' string, causing the browser to download styles in non-deterministic order. Omitting 'integrity' and 'crossOrigin' bypasses Subresource Integrity, allowing CDN compromises to inject malicious code while triggering React hydration mismatches if the SSR-rendered head differs from client expectations.
```typescript
import React from 'react';

interface DynamicWidgetProps {
  themeUrl: string;
}

export const DynamicWidget: React.FC<DynamicWidgetProps> = ({ themeUrl }) => {
  // ANTI-PATTERN: React 19 cannot order this stylesheet predictably without 'precedence'.
  // Lacks 'integrity' and 'crossOrigin', exposing the client to SRI bypass and hydration churn.
  return (
    <section className="widget-container">
      <link rel="stylesheet" href={themeUrl} />
      <script async src="https://cdn.example.com/widget-chunk.js" />
      <p>Widget Content</p>
    </section>
  );
};
```

#### Production Standard (Correct)
> **Standard**: Declaring 'precedence="high"' allows React 19 to deterministically insert and manage the stylesheet in <head>, preventing FOUC and hydration variance. Strict 'integrity' hashes with 'crossOrigin="anonymous"' enforce cryptographic validation before stylesheet or script execution.
```typescript
import React from 'react';

interface ValidatedThemeAsset {
  href: string;
  integrity: `sha384-${string}` | `sha512-${string}`;
}

interface DynamicWidgetProps {
  theme: ValidatedThemeAsset;
}

const SCRIPT_CHUNK = {
  src: 'https://cdn.example.com/widget-chunk-v1.4.2.js',
  integrity: 'sha384-oqVuAfXRKap7fdgcCY5uykM6+R9GqQ8K/uxy9rx7HNQlGYl1kPzQho1wx4JwY8wC' as const,
};

export const DynamicWidget: React.FC<DynamicWidgetProps> = ({ theme }) => {
  // PRODUCTION INVARIANT: Validated SRI hashes, strict crossOrigin, and deterministic precedence
  return (
    <section className="widget-container">
      <link
        rel="stylesheet"
        href={theme.href}
        precedence="high"
        integrity={theme.integrity}
        crossOrigin="anonymous"
      />
      <script
        async
        src={SCRIPT_CHUNK.src}
        integrity={SCRIPT_CHUNK.integrity}
        crossOrigin="anonymous"
      />
      <p>Widget Content</p>
    </section>
  );
};
```
Recommended MCP Servers (mcp-serverlist.com)

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

Asset SRI Hasher MCP
Calculates and validates sha384/sha512 Subresource Integrity digests for remote static assets during automated generation.
Recommended Agent Skills (askills.dev)

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

React 19 Architecture Audit Skill
Static code analyzer verifying React 19 head hoisting precedence rules, hydration markers, and asset preloads.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: React 19 Document Head Metadata Hoisting and Subresource Integrity Pinning

React 19 Document Head Metadata Hoisting and Subresource Integrity Pinning defines an industrial-grade behavioral standard for frontend engineering. Enforces deterministic cryptographic Subresource Integrity (SRI) validation and explicit precedence tagging for dynamically hoisted stylesheets, scripts, and preloads in React 19. Prevents hydration mismatches, supply-chain script tampering, and unpinned layout shifts when the React runtime reconciles native DOM head tags against server-rendered asset manifests. 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: Dynamic head hoisting without cryptographic hash validation or missing React precedence markers. 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 DriftDynamic head hoisting without cryptographic hash validation or missing React precedence markers.Critical
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 supply an explicit 'precedence' attribute on all hoisted <link rel="stylesheet"> tags to allow React 19 to establish deterministic head injection order without hydration mismatch.

Engineers MUST ALWAYS supply an explicit 'precedence' attribute on all hoisted <link rel="stylesheet"> tags to allow React 19 to establish deterministic head injection order without hydration mismatch.

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 pair external CSS or async script hoisting with both 'integrity' (pinned sha384/sha512 hash) and 'crossOrigin="anonymous"' attributes to prevent cross-origin resource poisoning and SRI enforcement failure.

Engineers MUST ALWAYS pair external CSS or async script hoisting with both 'integrity' (pinned sha384/sha512 hash) and 'crossOrigin="anonymous"' attributes to prevent cross-origin resource poisoning and SRI enforcement failure.

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 NOT rely on side-effect DOM manipulations (e.g., document.head.appendChild or custom MutationObservers in useEffect) to inject head assets

Engineers MUST NOT rely on side-effect DOM manipulations (e.g., document.head.appendChild or custom MutationObservers in useEffect) to inject head assets; native React 19 hoisted elements or ReactDOM.preload/preinit APIs must be used.

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 NEVER hoist unhashed third-party resources dynamically without an immutable build-time or server-verified manifest lookup.

Components MUST NEVER hoist unhashed third-party resources dynamically without an immutable build-time or server-verified manifest lookup.

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

Hydration boundaries MUST maintain identical SRI hashes between Server-Side Rendering (SSR) and Client-Side Hydration (CSH)

Hydration boundaries MUST maintain identical SRI hashes between Server-Side Rendering (SSR) and Client-Side Hydration (CSH); injecting dynamic nonces or hashes that drift between SSR and client renders is 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.
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 Head Metadata Hoisting and Subresource Integrity Pinning critical for AI coding assistants?

Enforces deterministic cryptographic Subresource Integrity (SRI) validation and explicit precedence tagging for dynamically hoisted stylesheets, scripts, and preloads in React 19. Prevents hydration mismatches, supply-chain script tampering, and unpinned layout shifts when the React runtime reconciles native DOM head tags against server-rendered asset manifests. 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 (Dynamic head hoisting without cryptographic hash validation or missing React precedence markers.) 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