revealui-db

Separate NeonDB content data from Supabase vector data with enforced import boundaries.

4|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/RevealUIStudio/revealui --skill revealui-db
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revealui-db
Source: https://github.com/RevealUIStudio/revealui/tree/main/.agents/skills/revealui-db
Command: npx skills add https://github.com/RevealUIStudio/revealui --skill revealui-db

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces a strict separation between NeonDB (PostgreSQL) and Supabase (vector/storage) to prevent cross-database contamination, simplifying data governance and deployment.

Core Features & Use Cases

  • Dual-database architecture: clearly separates operational data (NeonDB) from vector/AI data (Supabase).
  • Boundary enforcement: restricts Supabase imports to designated modules to maintain DB-agnostic CMS logic.
  • Migration and schema guidance: provides a structured approach to data modeling and schema organization across both databases.
  • Developer guidance: promotes best practices for Drizzle ORM usage and cross-service data flows.

Quick Start

Initialize your project with the dual-database pattern by configuring NeonDB for content and Supabase for embeddings, then apply the boundary rule in your codebase.

Frequently Asked Questions about revealui-db

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I separate vector embeddings in Supabase from operational data in NeonDB?

To separate vector embeddings in Supabase from operational data in NeonDB, implement a dual-database architecture that isolates AI and vector data from content management data, preventing cross-database contamination and simplifying data governance.

What is the best way to enforce database import boundaries with Drizzle ORM?

The best way to enforce database import boundaries with Drizzle ORM is to restrict Supabase imports to designated modules, ensuring your DB-agnostic CMS logic remains separated from vector and AI storage operations.

When do I need a dual-database architecture for PostgreSQL and vector storage?

You need a dual-database architecture for PostgreSQL and vector storage when managing content data alongside AI memory, requiring clear data ownership and access scope to prevent cross-database contamination during deployment.

Can I use Supabase for vector embeddings while keeping content data in a separate PostgreSQL database?

Yes, you can use Supabase for vector embeddings while keeping content data in a separate NeonDB PostgreSQL database, applying structured folder organization and migration workflows to maintain clear data ownership boundaries.

How do I organize schema migrations for a dual-database setup using Drizzle ORM and Supabase?

To organize schema migrations for a dual-database setup using Drizzle ORM and Supabase, apply a structured approach to data modeling that maintains separate migration workflows for operational data and vector AI data.