react-router-v7

A set of coding instructions for React Router v7, a library for handling page routes in React applications. It requires route types to be imported from each route’s local ./+types folder.

In plain words
What is it for?
Use it when adding, renaming, or type-checking React Router v7 routes in TypeScript projects.
Why use it?
It prevents incorrect type imports and helps resolve missing-type errors by generating types with the typecheck command or development server.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/brookslybrand/react-router-cursor-rules/react-router-v7
Clone the repo
git clone --depth 1 https://github.com/brookslybrand/react-router-cursor-rules

Made for: Cursor.

Per session 3,054 This file is loaded in full into every session.
When invoked 3,054 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.03054 $0.03054
Opus 5 $0.01527 $0.01527
Sonnet 5 $0.00611 $0.00611
Haiku 4.5 $0.00305 $0.00305

Measured 2d ago against content hash 0e1fd95645c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

react-router-v7 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 2d 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/react-router-v7.mdc · 426 lines

How it starts

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

React Router v7 Framework Mode - Cursor Rules

🚨 CRITICAL: Route Type Imports - NEVER MAKE THIS MISTAKE

THE MOST IMPORTANT RULE: ALWAYS use ./+types/[routeName] for route type imports.

// ✅ CORRECT - ALWAYS use this pattern:
import type { Route } from "./+types/product-details";
import type { Route } from "./+types/product";
import type { Route } from "./+types/category";

// ❌ NEVER EVER use relative paths like this:
// import type { Route } from "../+types/product-details";  // WRONG!
// import type { Route } from "../../+types/product";       // WRONG!

If you see TypeScript errors about missing ./+types/[routeName] modules:

  1. IMMEDIATELY run typecheck to generate the types
  2. Or start the dev server which will auto-generate types
  3. NEVER try to "fix" it by changing the import path

Type Generation & Workflow

  • Run typecheck after adding/renaming any routes
  • Run typecheck if you see missing type errors
  • Types are auto-generated by @react-router/dev in ./+types/[routeName] relative to each route file
  • The dev server will also generate types automatically

Critical Package Guidelines

✅ CORRECT Packages:

  • react-router - Main package for routing components and hooks
  • @react-router/dev - Development tools and route configuration
  • @react-router/node - Node.js server adapter
  • @react-router/serve - Production server

❌ NEVER Use:

  • react-router-dom - Legacy package, use react-router instead
  • @remix-run/* - Old packages, replaced by @react-router/*
  • React Router v6 patterns - Completely different architecture

Essential Framework Architecture

Route Configuration (app/routes.ts)

import { type RouteConfig, index, route } from "@react-router/dev/routes";

export default [
  index("routes/home.tsx"),
  route("about", "routes/about.tsx"),
  route("products/:id", "routes/product.tsx", [
    index("routes/product-overview.tsx"),
    route("reviews", "routes/product-reviews.tsx"),
  ]),
  route("categories", "routes/categories-layout.tsx", [
    index("routes/categories-list.tsx"),
    route(":slug", "routes/category-details.tsx"),
  ]),
] satisfies RouteConfig;

Read the full file on GitHub · 426 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. 2d ago First seen · 426 lines · 3,054 tokens per session scan A 0e1fd95645c6

Subscribe to this mod's changes

react-router-v7 is a cursor rule published in the GitHub repository brookslybrand/react-router-cursor-rules (118 stars, last pushed 4mo ago), licensed MIT. It adds 3,054 tokens to every session, about $0.0153 per session on Opus 5. 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-30.