react19-patterns

react19-patterns is a cursor rule for Cursor from vibestackdev/vibe-stack. It costs 0 tokens per session (571 once invoked), scanned A, original, MIT.

A set of rules for common React 19 and Next.js 15 migration issues, including form status hooks and newer form-state APIs.

In plain words
What is it for?
Use it when upgrading or building React 19 and Next.js 15 applications with forms, Server Actions, and pending-submit states.
Why use it?
It helps avoid outdated patterns that silently fail or behave differently after upgrading these frameworks.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when upgrading or building React 19 and Next.js 15 applications with forms, Server Actions, and pending-submit states.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/vibestackdev/vibe-stack/react19-patterns
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/vibestackdev/vibe-stack

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for react19-patterns

README.md
[![agentmods](https://agentmods.dev/badge/rules/vibestackdev/vibe-stack/react19-patterns/github.svg)](https://agentmods.dev/rules/vibestackdev/vibe-stack/react19-patterns)
Your own site
<a href="https://agentmods.dev/rules/vibestackdev/vibe-stack/react19-patterns"><img src="https://agentmods.dev/badge/rules/vibestackdev/vibe-stack/react19-patterns/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for react19-patterns

Your own site · 80×15
<a href="https://agentmods.dev/rules/vibestackdev/vibe-stack/react19-patterns"><img src="https://agentmods.dev/badge/rules/vibestackdev/vibe-stack/react19-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 571 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00571
Opus 5.5 $0.00000 $0.00228
Sonnet 5.5 $0.00000 $0.00114
Haiku 4.5 $0.00000 $0.00057

Measured 1mo ago against content hash 5747cf9d418f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

react19-patterns scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/react19-patterns.mdc · 85 lines

How it starts

The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.

React 19 / Next.js 15 Migration Traps

RULE 1: useFormStatus Must Be Inside

useFormStatus() only works when the component using it is a CHILD of a <form> element that uses a Server Action. It does NOT work if used in the same component that renders the form.

// ❌ WRONG — useFormStatus returns { pending: false } always
'use client'
export function MyForm() {
  const { pending } = useFormStatus() // Always false here
  return (
    <form action={createItem}>
      <Button disabled={pending}>Submit</Button>
    </form>
  )
}

// ✅ CORRECT — extract the submit button to a child component
'use client'
import { useFormStatus } from 'react-dom'

function SubmitButton() {
  const { pending } = useFormStatus()
  return <Button disabled={pending}>{pending ? 'Saving...' : 'Submit'}</Button>
}

export function MyForm() {
  return (
    <form action={createItem}>
      <SubmitButton />
    </form>
  )
}

RULE 2: useActionState Replaces useFormState

useFormState is DEPRECATED in React 19. Use useActionState instead.

// ❌ DEPRECATED
import { useFormState } from 'react-dom'

// ✅ CORRECT — React 19
import { useActionState } from 'react'

const [state, formAction, isPending] = useActionState(serverAction, initialState)

RULE 3: ref Is a Regular Prop in React 19

forwardRef() is no longer required. ref is passed as a regular prop.

// ❌ DEPRECATED — verbose, unnecessary in React 19
const MyInput = forwardRef<HTMLInputElement, InputProps>((props, ref) => {
  return <input ref={ref} {...props} />
})

// ✅ CORRECT — React 19
function MyInput({ ref, ...props }: InputProps & { ref?: React.Ref<HTMLInputElement> }) {
  return <input ref={ref} {...props} />
}

RULE 4: use() Hook for Promises and Context

React 19 use() can unwrap Promises in render. Use it instead of useEffect for data fetching in client components.

// ✅ React 19 — use() for context (replaces useContext)
import { use } from 'react'
const theme = use(ThemeContext)

Read the full file on GitHub · 85 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 85 lines · 0 tokens per session scan A 5747cf9d418f

Subscribe to this mod's changes

react19-patterns is a cursor rule published in the GitHub repository vibestackdev/vibe-stack (8 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 571 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.