skills.rest
juanjaragavi
juanjaragaviCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

database

Design multi-database schemas with versioned migrations and tenant isolation.

Updated Jan 30, 2026
Search Tags:#database#postgresql#migrations#orm#data-modeling#bigquery#schema-design
One-click install
npx skills add https://github.com/juanjaragavi/social-media-genius --skill database-juanjaragavi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: database
Source: https://github.com/juanjaragavi/social-media-genius/tree/main/.claude/skills/database
Command: npx skills add https://github.com/juanjaragavi/social-media-genius --skill database-juanjaragavi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides teams in designing, migrating, and maintaining multi-database schemas across Supabase PostgreSQL, Cloud SQL PostgreSQL, and BigQuery, ensuring consistency and scalability.

Core Features & Use Cases

  • Schema design principles for multi-tenant data with user_id ownership
  • Migration strategies, versioned scripts, and indexing conventions
  • Data access patterns and ORM / DAL usage across projects (route-genius, emailgenius, arbitrage-dashboard)

Quick Start

Create a new multi-database schema, write a versioned migration script, and implement a data access layer that works across Supabase, Cloud SQL, and BigQuery.

Frequently Asked Questions about database

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

FAQPage Schema
How do I design a multi-tenant PostgreSQL schema with strict user isolation?▼

Multi-tenant database schema design requires enforcing strict tenant isolation via user_id ownership and Row Level Security (RLS). This approach ensures data separation by applying access filters at the database level.

What is the best way to manage versioned database migrations across Supabase and Cloud SQL?▼

Versioned database migrations should be placed in a dedicated scripts/ directory to manage schemas across Supabase and Cloud SQL. This strategy maintains consistent versioning and indexing conventions across multiple properties.

How does BigQuery schema design differ from PostgreSQL for multi-database applications?▼

BigQuery schema design differs from PostgreSQL by focusing on analytical data modeling rather than transactional schemas with RLS. Designing scalable multi-database schemas involves applying distinct indexing and data access patterns across both platforms.

Can I use JSONB columns in Supabase PostgreSQL for flexible data modeling?▼

Yes, JSONB usage is explicitly required for flexible data modeling in Supabase PostgreSQL schemas. It allows storing semi-structured data while maintaining the strict tenant isolation required by the data access layer.

How do I implement a data access layer pattern that works across PostgreSQL and BigQuery?▼

Implementing a clear Data Access Layer (DAL) pattern standardizes ORM usage and queries across PostgreSQL and BigQuery. This abstraction enforces consistent data retrieval and JSONB handling for projects like route-genius and arbitrage-dashboard.

Related Skills

Explore More Software Engineering Skills→
evolv3aievolv3ai
3

django-cloud-sql-postgres

Deploy Django applications on Google App Engine Standard with Cloud SQL PostgreSQL.

Community
Advanced
AHMADJAN-NewAHMADJAN-New

nazim-migrations

Enforce Nazim database migration patterns for multi-tenancy and secure SQL.

Community
Intermediate
qazuorqazuor

drizzle-patterns

Standardize PostgreSQL schema, relations, and queries with Drizzle ORM.

Community
Advanced
NelkitNelkit
1

alembic-migration

Automate PostgreSQL schema changes with SQLAlchemy ORM and Alembic migrations.

Community
Intermediate