ai-collaboration Cursor ruleA
ai-collaboration from vibestackdev/vibe-stack is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add vibestackdev/vibe-stack/.cursor/rules/ai-collaboration.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/ai-collaboration.mdc- Versions recorded
- 2
- Latest version
- git:20260401.56e571e, committed Apr 1, 2026
- First version recorded
- Mar 30, 2026
- Size
- 3,309 bytes
- Repository stars
- 8
- License
- MIT
Instructions for AI agent code generation workflow.
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
# AI Collaboration Guidelines ## The 3-Stage Agentic Loop Every code generation task MUST follow this loop: ### Stage 1: PLAN (gather context first) Before writing ANY code, the AI MUST: 1. Read the relevant source files to verify current state — do NOT rely on memory 2. Identify which `.cursor/rules/` files apply to this task 3. List the files to modify and explain why 4. Do NOT write code yet Prompt template: ``` Analyze the current codebase and plan how to implement [feature]. List the files you'll modify and why. Don't write code yet. ``` ### Stage 2: IMPLEMENT (follow constraints) When generating code: - Follow ALL active `.cursor/rules/` constraints - If unsure about auth patterns, re-read `supabase-auth-security.mdc` - If unsure about params/layouts, re-read `nextjs15-params.mdc` - Use `unknown` + Zod validation instead of `any` for external data - Return `ActionResponse<T>` from all Server Actions (see below) ### Stage 3: VERIFY (confirm before declaring done) After generating code, the AI MUST self-check: - [ ] No `getSession()` on the server (MUST be `getUser()`) - [ ] No synchronous `params` or `searchParams` access …
Read the whole file at its exact version.
How to install
mdr add vibestackdev/vibe-stack/.cursor/rules/ai-collaboration.mdc@sha256:39de764d2ae5d331The 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_pgabopzilwobbba2)
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/ai-collaboration.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 ai-collaboration.mdc from somewhere else? Ask it: where did my ai-collaboration.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 2 versions of this file, between Mar 30, 2026 and Apr 1, 2026, about one every 2 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260401.56e571e latest | 2026-04-01 | 56e571e | 3,309 B | A | view · diff |
| git:20260330.dd1a8a9 | 2026-03-30 | dd1a8a9 | 899 B | A | view |
Installed this file, say at ai-collaboration.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 (3309 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_pgabopzilwobbba2 GET https://markdownregistry.com/api/v1/resolve?ref=vibestackdev/vibe-stack/.cursor/rules/ai-collaboration.mdc GET https://markdownregistry.com/api/v1/blob/39de764d2ae5d331a96b3733a38ded7b2321d37dc703f18ed6d97fb6ce589015
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.