env-management Cursor ruleA
env-management from vibestackdev/vibe-stack is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add vibestackdev/vibe-stack/.cursor/rules/env-management.mdc@git:20260330.1081646Pins git:20260330.1081646 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/env-management.mdc- Versions recorded
- 1
- Latest version
- git:20260330.1081646, committed Mar 30, 2026
- Size
- 2,001 bytes
- Repository stars
- 8
- License
- MIT
Environment variable management and secrets handling.
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
# Environment Variable Management
## Classification Rules
| Prefix | Visibility | Use For |
|--------|-----------|---------|
| `NEXT_PUBLIC_` | Client + Server | Non-sensitive public values (Supabase URL, Stripe publishable key) |
| No prefix | Server Only | ALL secrets (API keys, webhook secrets, database URLs) |
## NEVER Expose These to the Client
```
STRIPE_SECRET_KEY → Server only (NEVER NEXT_PUBLIC_)
STRIPE_WEBHOOK_SECRET → Server only
SUPABASE_SERVICE_ROLE_KEY → Server only (admin bypass key)
RESEND_API_KEY → Server only
DATABASE_URL → Server only
```
## Safe for Client
```
NEXT_PUBLIC_SUPABASE_URL → Public Supabase endpoint
NEXT_PUBLIC_SUPABASE_ANON_KEY → Rate-limited client key (RLS protects data)
NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY → Stripe public key (payment form only)
NEXT_PUBLIC_APP_URL → Your app's URL
```
## Validation Pattern
Use `src/lib/env.ts` to validate at startup:
```typescript
function getEnvVar(key: string, required = true): string {
const value = process.env[key]
if (!value && required) {
throw new Error(`❌ Missing required env var: ${key}`)
}
return value ?? ''
}
```
…Read the whole file at its exact version.
How to install
mdr add vibestackdev/vibe-stack/.cursor/rules/env-management.mdc@sha256:c2ad01718d76dff1The line at the top of this page pins the label git:20260330.1081646, 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_fcasegllt6hsipof)
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/env-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 env-management.mdc from somewhere else? Ask it: where did my env-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 Mar 30, 2026.
Watch this file (sign in, one email per new version)
Installed this file, say at env-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 (2001 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_fcasegllt6hsipof GET https://markdownregistry.com/api/v1/resolve?ref=vibestackdev/vibe-stack/.cursor/rules/env-management.mdc GET https://markdownregistry.com/api/v1/blob/c2ad01718d76dff1fa7b9bed3794c32f76888fac46a430c558d0037116e68043
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