business-data-model-designer

Design Supabase PostgreSQL schemas with RLS policies and migration plans.

3|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/anthril/official-claude-plugins --skill business-data-model-designer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: business-data-model-designer
Source: https://github.com/anthril/official-claude-plugins/tree/main/plugins/knowledge-engineering/skills/business-data-model-designer
Command: npx skills add https://github.com/anthril/official-claude-plugins --skill business-data-model-designer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, production-ready approach to designing relational data models for Supabase (PostgreSQL) apps, including ERD generation, migration sequencing, RLS patterns, and security-aware schemas.

Core Features & Use Cases

  • Entity identification and normalisation with 3NF-compliant schemas
  • Supabase-specific design guidance: RLS, policies, enums, and extension types
  • Generation of ordered migrations, indexes, and seed data
  • ERD diagrams and documentation for stakeholder review

Quick Start

Provide a business domain description and requirements to generate a complete data model for your Supabase project.

Frequently Asked Questions about business-data-model-designer

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

FAQPage Schema
How do I design a data model for a multi-tenant SaaS application in Supabase?

Designing a multi-tenant SaaS data model in Supabase involves generating normalised 3NF-compliant PostgreSQL schemas, defining row-level security (RLS) policies, and creating ordered migrations with appropriate indexing and access control patterns.

How do I generate PostgreSQL migrations with RLS policies for my Supabase project?

Generating PostgreSQL migrations with RLS policies produces a sequenced deployment plan that includes table schemas, enums, JSONB columns, helper functions, triggers, and seed data, ready for direct integration into a Supabase project.

What is the best way to structure PostgreSQL schemas for multi-tenant SaaS to ensure data isolation?

The best way to structure PostgreSQL schemas for multi-tenant SaaS is applying normalised relational design combined with robust RLS policies and access control patterns, ensuring data isolation, auditability, and scalability across tenants.

Does this data modeling approach support JSONB usage and custom enums in Supabase?

Yes, this data modeling approach supports Supabase extension types by incorporating JSONB usage for flexible data storage and custom enums for strict data validation within the generated migration scripts.

Can I get an ERD diagram and documentation for stakeholder review when designing Supabase databases?

Yes, designing Supabase databases includes generating ERD diagrams and inline documentation alongside the normalised schemas and migration plans, providing clear visual references for stakeholder review.

How do I add auditability and automatic timestamps to a Supabase PostgreSQL schema?

You add auditability and automatic timestamps to a Supabase PostgreSQL schema by defining helper functions and triggers within the migration sequence, tracking data changes securely without manual intervention.