菜单
RevealUI database conventions for any task involving database, schema, query, migration, Drizzle ORM, Neon, PostgreSQL, pgvector, vectors, embeddings, or data modeling. Covers the single Neon-primary database and its pgvector tables.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | revealui-db |
| description | RevealUI database conventions for any task involving database, schema, query, migration, Drizzle ORM, Neon, PostgreSQL, pgvector, vectors, embeddings, or data modeling. Covers the single Neon-primary database and its pgvector tables. |
RevealUI runs a single Neon-primary PostgreSQL database (Drizzle ORM), with vector data (agent memories + RAG) stored in that same database via pgvector and live sync provided by ElectricSQL:
| Database | Client | Purpose |
|---|---|---|
| Neon (PostgreSQL) | @neondatabase/serverless (falls back to node-postgres for localhost) | All data: collections, users, sessions, orders, products, plus pgvector tables (agent memories, RAG) |
| ElectricSQL | @electric-sql | Live read-path sync over the same Neon database |
There is no second database client. All persistence goes through the single Drizzle/Neon client (@revealui/db); vector data lives in pgvector on the same Neon database, so there is no separate vector/auth client to import. (A customer-facing Supabase MCP adapter exists for connecting a customer's OWN Supabase project as a selectable data source — it is never RevealUI's internal store.)
packages/db/src/schema/
├── collections/ # NeonDB: content collections
├── users/ # NeonDB: user management
├── commerce/ # NeonDB: products, orders, pricing
├── sessions/ # NeonDB: auth sessions
├── vector/ # Neon (pgvector): embeddings, similarity search
└── auth/ # Neon: session-based auth (no separate auth store)
import { db } from '@revealui/db'
import { posts } from '@revealui/db/schema'
const results = await db.select().from(posts).where(eq(posts.status, 'published'))
// Vector tables live on the same Neon database (pgvector)
import { db } from '@revealui/db'
import { agentMemories } from '@revealui/db/schema'
const results = await db.select().from(agentMemories).orderBy(cosineDistance(agentMemories.embedding, queryEmbedding)).limit(5)
The pnpm validate:structure script checks package/import-boundary conventions.
CI runs this as part of phase 1 (warn-only — violations are flagged but don't block builds).
To check locally:
pnpm validate:structure
When adding new features:
packages/db/src/schema/ + use Drizzlepackages/db/src/schema/vector.ts (pgvector on the same Neon database) + use DrizzleRevealUI coding conventions for any code task — writing, editing, reviewing, creating, fixing, refactoring, changing, adding, or updating TypeScript, React, CSS, or config files. Covers TypeScript strict mode, ES Modules, Biome formatting, Tailwind v4 syntax, conventional commits, monorepo workspace protocol, feature gating, parameterization, and unused declaration policy.
Systematic debugging workflow for RevealUI. Use when encountering any bug, test failure, unexpected behavior, error, or broken functionality. Prevents shotgun debugging.
RevealUI deployment guide — Vercel configuration, GitHub Actions deploy workflow, secret management, domain aliasing, and troubleshooting. Invoke when working on deploy.yml, vercel.json, deployment secrets, domain configuration, or debugging deploy failures.
Code review checklist for RevealUI. Use when reviewing code, completing a feature, checking quality, or before committing. Invoke explicitly with $revealui-review.
RevealUI safety guardrails for any code task — editing, writing, creating, fixing, refactoring, changing, adding, updating, or removing files. Protects credentials, enforces import boundaries, ensures code quality, and verifies work before completion.
Test-driven development workflow for RevealUI. Use when implementing any feature, fixing bugs, adding functionality, or writing new code. Enforces write-test-first, red-green-refactor cycle. Works with Vitest and React Testing Library.