backend-database

Design and optimize PostgreSQL/Supabase databases with RLS policies and RBAC.

1|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/coreymaypray/sloth-skill-tree --skill backend-database-coreymaypray
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-database
Source: https://github.com/coreymaypray/sloth-skill-tree/tree/main/plugins/maycrest-automate/skills/backend-database
Command: npx skills add https://github.com/coreymaypray/sloth-skill-tree --skill backend-database-coreymaypray

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PostgreSQL/Supabase database design, schema setup, RLS policies, performance optimization, and pricing guidance for multi-project environments.

Core Features & Use Cases

  • Database Design & Normalization: Design scalable schemas with normalization, indexing, and data integrity for multi-tenant apps.
  • RLS & RBAC Implementation: Define row-level and role-based access controls to protect per-tenant data.
  • Performance & Cost Guidance: Tune queries, plan capacity, and select cost-effective Supabase plans for client projects.
  • Use Case: Example: set up a multi-tenant database for a client project with per-tenant schemas, RBAC, and optimized indexing.

Quick Start

Configure a new multi-tenant database for a client project in Supabase.

Frequently Asked Questions about backend-database

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

FAQPage Schema
How do I design a multi-tenant Postgres schema with proper data isolation?

Design multi-tenant Postgres schemas by normalizing to 3NF, defining per-tenant schemas, and implementing row-level security policies to isolate client data. This approach ensures data integrity and scalable multi-project deployments across Supabase.

What is the best way to configure RLS and RBAC policies in Supabase?

Configure Supabase RLS and RBAC by defining role-based access controls and row-level security policies to protect per-tenant data. This ensures users only access rows matching their assigned roles within the normalized database schema.

How do I optimize PostgreSQL performance and query speed for multi-project deployments?

Optimize PostgreSQL performance by tuning queries, planning capacity, and applying optimized indexing strategies tailored for multi-tenant apps. Proper indexing and normalization maintain query speed as client project data scales.

Does this database design approach support versioned migrations and 3NF normalization?

Yes, the database design approach satisfies requirements for normalized 3NF schemas and versioned migrations. It provides documented best practices for setting up scalable schemas with strict data integrity for client applications.

How do I select cost-effective Supabase plans for multi-tenant client apps?

Select cost-effective Supabase plans by evaluating capacity planning needs, performance tuning requirements, and per-tenant data storage estimates. This guidance helps manage costs across multiple client project deployments effectively.