project-context Cursor ruleA
project-context from vibestackdev/vibe-stack is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add vibestackdev/vibe-stack/.cursor/rules/project-context.mdc@git:20260330.dd1a8a9Pins git:20260330.dd1a8a9 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/project-context.mdc- Versions recorded
- 1
- Latest version
- git:20260330.dd1a8a9, committed Mar 30, 2026
- Size
- 2,081 bytes
- Repository stars
- 8
- License
- MIT
Core project context — tech stack, folder structure, and global conventions.
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
# Vibe Stack — Project Context ## Tech Stack - Framework: Next.js 15 (App Router) with React 19 - Language: TypeScript (strict mode) - Styling: Tailwind CSS + shadcn/ui components - Database: Supabase (PostgreSQL + RLS) - Auth: Supabase SSR (cookie-based, @supabase/ssr) - Validation: Zod - Payments: Stripe (server-side only) - Email: Resend - Icons: lucide-react ## Architecture Rules 1. Default to Server Components. Only add 'use client' when the component needs interactivity. 2. Push 'use client' to the smallest leaf component possible. 3. All data fetching happens in Server Components or Server Actions. 4. All mutations happen via Server Actions, never client-side fetch(). 5. All external input MUST be validated with Zod schemas. 6. Never use getSession() on the server — always use getUser(). 7. All database tables MUST have Row Level Security (RLS) enabled. ## Folder Structure ``` src/ ├── app/ # Next.js App Router pages & layouts │ ├── (auth)/ # Auth route group (login, signup) │ ├── dashboard/ # Protected pages (behind middleware) │ └── api/ # Route handlers (webhooks, public APIs) ├── components/ # Reusable React components …
Read the whole file at its exact version.
How to install
mdr add vibestackdev/vibe-stack/.cursor/rules/project-context.mdc@sha256:c975a5e110a2032bThe line at the top of this page pins the label git:20260330.dd1a8a9, 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_lax5f4vpnxmghb4x)
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/project-context.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 project-context.mdc from somewhere else? Ask it: where did my project-context.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 project-context.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 (2081 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_lax5f4vpnxmghb4x GET https://markdownregistry.com/api/v1/resolve?ref=vibestackdev/vibe-stack/.cursor/rules/project-context.mdc GET https://markdownregistry.com/api/v1/blob/c975a5e110a2032bdf2eddef4432bea94606fffac23a19f288ce060312edfbf6
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