memstack-development-database-architect

Design PostgreSQL/Supabase schemas with RLS policies and migration SQL.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/jtucker9/mystuff --skill memstack-development-database-architect-jtucker9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memstack-development-database-architect
Source: https://github.com/jtucker9/mystuff/tree/main/skills/development/database-architect
Command: npx skills add https://github.com/jtucker9/mystuff --skill memstack-development-database-architect-jtucker9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designers and engineers often need to translate feature concepts into production-ready PostgreSQL schemas, with correct table relationships, access controls (RLS), and migration scripts, without introducing errors.

Core Features & Use Cases

  • Produces production-ready Supabase/Postgres schemas with proper naming, table relationships, RLS policies, and indexes.
  • Outputs ready-to-run migration SQL for new features and schema changes.
  • Use cases include database design for new features, ERD modeling, and implementing migrations in evolving applications.

Quick Start

Provide a production-ready Postgres schema and corresponding migration SQL for a new feature.

Frequently Asked Questions about memstack-development-database-architect

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

FAQPage Schema
How do I design a production-ready Postgres schema with RLS policies for a new feature?

Design a production-ready Postgres schema by generating tables with properly named relationships, RLS policies, indexes, and ready-to-run migration SQL. This approach translates feature concepts into structured database architectures without introducing manual errors.

What is the best way to generate Supabase migration scripts for new database structures?

The best way to generate Supabase migration scripts is to output ready-to-run migration SQL alongside your schema design. This ensures your new database structures and schema changes are version-controlled and deployed accurately.

How do you model ERDs and table relationships for PostgreSQL?

Model ERDs and table relationships for PostgreSQL by defining production-ready schemas with proper naming conventions. The process maps feature concepts into structured tables and correctly named relationships to visualize and implement the database architecture.

Does this approach work for both new database structures and evolving application migrations?

Yes, this approach works for both creating new database structures and implementing migrations in evolving applications. It produces production-ready Supabase schemas and migration scripts to handle schema changes seamlessly across feature updates.

Can I use this to set up Supabase access controls and indexes automatically?

Yes, you can set up Supabase access controls and indexes automatically. The schema generation process includes producing proper RLS policies for access controls and database indexes directly within the outputted PostgreSQL schema and migration SQL.