context-management Cursor ruleA
context-management from vibestackdev/vibe-stack is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add vibestackdev/vibe-stack/.cursor/rules/context-management.mdc@git:20260401.56e571ePins git:20260401.56e571e 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/context-management.mdc- Versions recorded
- 1
- Latest version
- git:20260401.56e571e, committed Apr 1, 2026
- Size
- 1,964 bytes
- Repository stars
- 8
- License
- MIT
Context window management — prevents AI from losing track during long sessions.
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
# Context Management Rules ## RULE 1: Break Large Tasks Into Sub-Tasks If a feature requires changes to more than 4 files, break it into sequential sub-tasks. Complete and verify each sub-task before starting the next. Example — "Add a blog feature with CRUD": 1. Sub-task 1: Database migration + RLS policies 2. Sub-task 2: Server Actions (create, read, update, delete) 3. Sub-task 3: UI components (list, detail, form) 4. Sub-task 4: Route handlers + API endpoints 5. Sub-task 5: Integration testing ## RULE 2: Summarize Before Continuing If the conversation has been going for more than 5 turns, summarize what has been done and what remains before generating more code. Template: ``` Before continuing, let me summarize: ✅ Completed: [list of completed items] 🔄 In progress: [current item] 📋 Remaining: [list of remaining items] ``` ## RULE 3: Reference Files By Full Path When discussing code, ALWAYS use the full path relative to the project root. This prevents confusion between similarly named files. ✅ CORRECT: "Update `src/app/dashboard/page.tsx`" ❌ WRONG: "Update the dashboard page" ✅ CORRECT: "Import from `@/lib/supabase/server`" ❌ WRONG: "Import the Supabase client" …
Read the whole file at its exact version.
How to install
mdr add vibestackdev/vibe-stack/.cursor/rules/context-management.mdc@sha256:77cd9736ab591948The line at the top of this page pins the label git:20260401.56e571e, 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_j5ve7yjhbvlikbvf)
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/context-management.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 context-management.mdc from somewhere else? Ask it: where did my context-management.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 Apr 1, 2026.
Watch this file (sign in, one email per new version)
Installed this file, say at context-management.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 (1964 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_j5ve7yjhbvlikbvf GET https://markdownregistry.com/api/v1/resolve?ref=vibestackdev/vibe-stack/.cursor/rules/context-management.mdc GET https://markdownregistry.com/api/v1/blob/77cd9736ab59194805bd79cae7558051b8d705f0e36d5f136ce4a7b5705904d6
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.
More from vibestackdev/vibe-stack
Every file in vibestackdev/vibe-stack