single-dev-server Cursor ruleA
single-dev-server from vanshyadav1408/omentir is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add vanshyadav1408/omentir/.cursor/rules/single-dev-server.mdc@git:20260828.d3bb9bcPins git:20260828.d3bb9bc in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Cursor rule
- Repository
- vanshyadav1408/omentir
- Path
.cursor/rules/single-dev-server.mdc- Versions recorded
- 1
- Latest version
- git:20260828.d3bb9bc, committed Aug 28, 2026
- Size
- 924 bytes
- Repository stars
- 48
- License
- MIT
Never start a second localhost Next.js server. Use the existing one.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# One localhost only Never start a second `bun run dev`, `next dev`, or `next start`. Two Next.js processes share `.next`. That corrupts the Turbopack cache (missing `.sst` files, `/_app` panics, 500s on automation ticks). ## Before you start anything 1. Check Cursor terminals and listeners on 3000, 3001, and 3002. 2. If a Next.js server is already running, use that URL. Do not spawn another. 3. If 3000 is taken, Next will silently bind 3001 or 3002. That is a second server. Do not do that. ## If the existing server is dead or the cache is corrupt 1. Stop every `next` / `next-server` process first. 2. Only then `rm -rf .next` if you saw SST or Turbopack cache errors. 3. Start exactly one `bun run dev`. Verify against the existing server (`http://localhost:3000` unless its own logs say otherwise).
Read the whole file at its exact version.
How to install
mdr add vanshyadav1408/omentir/.cursor/rules/single-dev-server.mdc@sha256:862c7aa1d78931deThe line at the top of this page pins the label git:20260828.d3bb9bc, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_5hvq33jaof7rh4g4)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 28, 2026.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (924 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
vanshyadav1408/omentir · 48 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5hvq33jaof7rh4g4 GET https://markdownregistry.com/api/v1/resolve?ref=vanshyadav1408/omentir/.cursor/rules/single-dev-server.mdc GET https://markdownregistry.com/api/v1/blob/862c7aa1d78931deaf988983b5b5affc5be1071b62e5c48c783126b077aede66
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: Cursor rules vs AGENTS.md · which agent file does what.