database-design Cursor ruleA
database-design from vibestackdev/vibe-stack is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add vibestackdev/vibe-stack/.cursor/rules/database-design.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/database-design.mdc- Versions recorded
- 1
- Latest version
- git:20260330.1081646, committed Mar 30, 2026
- Size
- 2,295 bytes
- Repository stars
- 8
- License
- MIT
Database schema design patterns for Supabase with proper types and relationships.
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
# Database Design Patterns ## Table Naming - Use `snake_case` for tables and columns: `user_profiles`, `created_at` - NEVER use camelCase in SQL: `userId` → WRONG, `user_id` → CORRECT - Use plural table names: `profiles`, `posts`, `comments` ## Required Columns (Every Table) ```sql CREATE TABLE public.example ( id UUID DEFAULT gen_random_uuid() PRIMARY KEY, -- your columns here created_at TIMESTAMPTZ DEFAULT NOW() NOT NULL, updated_at TIMESTAMPTZ DEFAULT NOW() NOT NULL ); ``` ALWAYS include `id`, `created_at`, and `updated_at`. ALWAYS use UUID for primary keys (not serial/integer). ALWAYS use TIMESTAMPTZ (not TIMESTAMP) for timezone safety. ## Foreign Key Pattern ```sql -- Always reference auth.users for user ownership user_id UUID REFERENCES auth.users(id) ON DELETE CASCADE NOT NULL ``` Use `ON DELETE CASCADE` for user-owned data. Use `ON DELETE SET NULL` for optional relationships. ## RLS Template (Copy This Every Time) ```sql ALTER TABLE public.example ENABLE ROW LEVEL SECURITY; -- Users can only see their own data CREATE POLICY "Users own data" ON public.example FOR ALL USING (auth.uid() = user_id); -- Or for public read + owner write: …
Read the whole file at its exact version.
How to install
mdr add vibestackdev/vibe-stack/.cursor/rules/database-design.mdc@sha256:519a4b26b26bcb6eThe 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_gff6dhsfr5waix4w)
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/database-design.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 database-design.mdc from somewhere else? Ask it: where did my database-design.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 database-design.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 (2295 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_gff6dhsfr5waix4w GET https://markdownregistry.com/api/v1/resolve?ref=vibestackdev/vibe-stack/.cursor/rules/database-design.mdc GET https://markdownregistry.com/api/v1/blob/519a4b26b26bcb6e7e0d2fbdb1be2d5ab0e13045c7b88f0f75fb1ede7c63a971
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