mern-stack

A set of coding guidelines for MERN applications: MongoDB for data, Express and Node.js for the server, and React for the interface. It also covers Mongoose, a tool for working with MongoDB, and a monorepo, which keeps related frontend and backend projects together.

In plain words
What is it for?
Use it when building or reviewing a MERN web application, including its frontend, backend, database models, API routes, shared types, and project layout.
Why use it?
It gives the coding agent a consistent structure and conventions for projects that combine a React frontend with a Node.js backend. This reduces decisions about where code belongs and how the parts connect.

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/mern-stack
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,960 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.02960
Opus 5 $0.00000 $0.01480
Sonnet 5 $0.00000 $0.00592
Haiku 4.5 $0.00000 $0.00296

Measured yesterday against content hash f01f3179dd53, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mern-stack 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 yesterday.

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/stacks/mern-stack.mdc · 521 lines

How it starts

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

MERN Stack Best Practices

Overview

Layer Technology Purpose
Database MongoDB Document database
Backend Express.js Node.js web framework
Frontend React UI library
Runtime Node.js JavaScript runtime
ODM Mongoose MongoDB object modeling

Related rules: nodejs.mdc, react-19.mdc, typescript.mdc


Project Structure

Monorepo Structure

project/
├── client/                 # React frontend
│   ├── src/
│   │   ├── components/
│   │   ├── hooks/
│   │   ├── pages/
│   │   ├── services/       # API calls
│   │   ├── stores/         # State management
│   │   └── types/
│   ├── package.json
│   └── vite.config.ts
├── server/                 # Express backend
│   ├── src/
│   │   ├── controllers/
│   │   ├── middleware/
│   │   ├── models/
│   │   ├── routes/
│   │   ├── services/
│   │   ├── types/
│   │   ├── utils/
│   │   └── index.ts
│   └── package.json
├── shared/                 # Shared types/utils
│   └── types/
└── package.json            # Root workspace

Express Backend

App Setup

// server/src/index.ts
import express from 'express'
import cors from 'cors'
import helmet from 'helmet'
import mongoose from 'mongoose'
import { config } from './config'
import { errorHandler } from './middleware/errorHandler'
import { userRoutes } from './routes/user'
import { postRoutes } from './routes/post'

const app = express()

// Middleware
app.use(helmet())
app.use(cors({ origin: config.clientUrl, credentials: true }))
app.use(express.json())

// Routes
app.use('/api/users', userRoutes)
app.use('/api/posts', postRoutes)

// Error handling
app.use(errorHandler)

// Database connection
mongoose.connect(config.mongoUri)
  .then(() => console.log('Connected to MongoDB'))
  .catch((err) => console.error('MongoDB connection error:', err))

app.listen(config.port, () => {
  console.log(`Server running on port ${config.port}`)
})

Mongoose Models

Read the full file on GitHub · 521 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. yesterday First seen · 521 lines · 0 tokens per session scan A f01f3179dd53

Subscribe to this mod's changes

mern-stack 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,960 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.