database-ops

Design PostgreSQL schemas with RLS, migrations, and multi-tenant access control.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/CutTheChexx/open-rx --skill database-ops-cutthechexx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-ops
Source: https://github.com/CutTheChexx/open-rx/tree/main/skills/database-ops
Command: npx skills add https://github.com/CutTheChexx/open-rx --skill database-ops-cutthechexx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Design and implement robust PostgreSQL schemas for multi-tenant apps, enabling secure access, scalable performance, and reliable migrations.

Core Features & Use Cases

  • Schema design principles for users, organizations, projects, leads, audits, and more.
  • Row Level Security (RLS) enablement and policy patterns for multi-tenant security.
  • Migrations, backups, performance optimizations, and type generation for client apps.

Quick Start

Configure a multi-tenant PostgreSQL schema by enabling RLS on core tables, apply initial migrations, and validate access policies.

Frequently Asked Questions about database-ops

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

FAQPage Schema
How do I set up multi-tenant Row Level Security in PostgreSQL?

Multi-tenant Row Level Security (RLS) in PostgreSQL is established by enabling RLS on core tables and applying policy patterns that enforce data isolation. This approach secures access control for organizations, projects, and user data.

What is the best way to manage reliable database migrations for a multi-tenant schema?

Reliable database migrations for a multi-tenant schema are managed by applying structured migration patterns alongside schema governance best practices. This maintains auditability and data integrity during schema evolution across production environments.

How do I design a PostgreSQL schema for organizations and audits?

Designing a PostgreSQL schema for organizations and audits involves establishing structured relationships for users, projects, and leads. It enforces schema design principles that guarantee scalable performance and auditability for data-heavy applications.

Does this approach work with Supabase for multi-tenant access control?

Yes, this approach works with Supabase for multi-tenant access control by leveraging PostgreSQL RLS policies natively supported by the platform. It enables strict data isolation and secure client access within Supabase.

When do I need to enforce strict schema governance and data isolation?

Strict schema governance and data isolation are needed when building data-heavy, multi-tenant systems where auditability and data security are critical. It prevents unauthorized cross-tenant access and maintains reliable production database operations.