remix

A set of recommendations for Remix version 2 and React Router version 7 applications. Remix is a web framework that uses loaders for reading data and actions for handling changes.

In plain words
What is it for?
It is for organizing Remix routes, fetching data with loaders, handling mutations with actions, building progressively enhanced forms, and styling with Tailwind CSS.
Why use it?
It gives the project a consistent way to load data, process form submissions, structure routes, and support users whose browser features are limited.

Cursor rule

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/renvia-code/best-cursor-rules/remix
Clone the repo
git clone --depth 1 https://github.com/Renvia-code/best-cursor-rules
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 2,499 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.02499
Opus 5 $0.00000 $0.01249
Sonnet 5 $0.00000 $0.00500
Haiku 4.5 $0.00000 $0.00250

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

Security

Grade A, and why

remix 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.

rules/frameworks/remix.mdc · 440 lines

How it starts

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

Remix Best Practices

Overview

Aspect Recommendation
Version Remix v2 / React Router v7
Data Loading Loaders
Mutations Actions
Forms <Form> with progressive enhancement
Styling Tailwind CSS

Project Structure

app/
├── routes/
│   ├── _index.tsx           # Home route (/)
│   ├── about.tsx            # /about
│   ├── users._index.tsx     # /users
│   ├── users.$id.tsx        # /users/:id
│   ├── users.$id.edit.tsx   # /users/:id/edit
│   └── api.users.tsx        # /api/users (resource route)
├── components/
│   ├── ui/
│   └── ...
├── lib/
│   ├── db.server.ts
│   └── session.server.ts
├── root.tsx
└── entry.server.tsx

Loaders (Data Fetching)

Basic Loader

// app/routes/users._index.tsx
import type { LoaderFunctionArgs } from '@remix-run/node'
import { json } from '@remix-run/node'
import { useLoaderData } from '@remix-run/react'
import { db } from '~/lib/db.server'

export async function loader({ request }: LoaderFunctionArgs) {
  const url = new URL(request.url)
  const page = Number(url.searchParams.get('page')) || 1
  
  const users = await db.user.findMany({
    take: 20,
    skip: (page - 1) * 20,
  })
  
  return json({ users, page })
}

export default function UsersPage() {
  const { users, page } = useLoaderData<typeof loader>()
  
  return (
    <div>
      <h1>Users</h1>
      <ul>
        {users.map((user) => (
          <li key={user.id}>{user.name}</li>
        ))}
      </ul>
    </div>
  )
}

Loader with Params

// app/routes/users.$id.tsx
import type { LoaderFunctionArgs } from '@remix-run/node'
import { json } from '@remix-run/node'
import { useLoaderData } from '@remix-run/react'
import invariant from 'tiny-invariant'

export async function loader({ params }: LoaderFunctionArgs) {
  invariant(params.id, 'Missing user ID')
  
  const user = await db.user.findUnique({
    where: { id: params.id },
  })
  
  if (!user) {
    throw new Response('Not Found', { status: 404 })
  }
  
  return json({ user })
}

Read the full file on GitHub · 440 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 · 440 lines · 0 tokens per session scan A 72306040d9e3

Subscribe to this mod's changes

remix is a cursor rule published in the GitHub repository Renvia-code/best-cursor-rules (12 stars, last pushed 9mo ago), licensed CC0-1.0. It costs nothing until one of its globs matches a file; then it loads 2,499 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-30.