caching-revalidation Cursor ruleA
caching-revalidation from vibestackdev/vibe-stack is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add vibestackdev/vibe-stack/.cursor/rules/caching-revalidation.mdc@git:20260330.dc27980Pins git:20260330.dc27980 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Cursor rule
- Repository
- vibestackdev/vibe-stack
- Path
.cursor/rules/caching-revalidation.mdc- Versions recorded
- 1
- Latest version
- git:20260330.dc27980, committed Mar 30, 2026
- Size
- 1,703 bytes
- Repository stars
- 8
- License
- MIT
Next.js caching and revalidation best practices.
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
# Caching & Revalidation
## Default Behavior
Next.js 15 has specific caching defaults. AI models often get these wrong.
## Rules
### Server Components - Data Fetching
For dynamic data that changes frequently:
```typescript
// Force fresh data on every request
const data = await fetch(url, { cache: 'no-store' })
// Or revalidate every 60 seconds:
const data = await fetch(url, { next: { revalidate: 60 } })
```
### Route Segment Config
For pages that must always show fresh data:
```typescript
// At the top of page.tsx or layout.tsx:
export const dynamic = 'force-dynamic' // Never cache this page
export const revalidate = 0 // Same as above
```
For static pages that rarely change:
```typescript
export const revalidate = 3600 // Revalidate every hour
```
### Server Actions — Always Revalidate
After mutations, ALWAYS revalidate affected paths:
```typescript
'use server'
import { revalidatePath } from 'next/cache'
export async function createPost(formData: FormData) {
// ... create post in database
revalidatePath('/posts') // ← NEVER forget this
revalidatePath('/dashboard') // ← Revalidate all affected pages
}
```
### Anti-Patterns
…Read the whole file at its exact version.
How to install
mdr add vibestackdev/vibe-stack/.cursor/rules/caching-revalidation.mdc@sha256:dcee97eeabc5ba99The line at the top of this page pins the label git:20260330.dc27980, 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_dniq2sul5au7e4bw)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in vibestackdev/vibe-stack/.cursor/rules/caching-revalidation.mdc since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of caching-revalidation.mdc from somewhere else? Ask it: where did my caching-revalidation.mdc come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Mar 30, 2026.
Watch this file (sign in, one email per new version)
Installed this file, say at caching-revalidation.mdc? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (1703 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
vibestackdev/vibe-stack · 8 stars · license MIT · pushed 2026-11-17 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_dniq2sul5au7e4bw GET https://markdownregistry.com/api/v1/resolve?ref=vibestackdev/vibe-stack/.cursor/rules/caching-revalidation.mdc GET https://markdownregistry.com/api/v1/blob/dcee97eeabc5ba9969a29019624c2f14dbd862e14a12028ca13a1e30977e606a
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.