database-schema-designer

Design relational database schemas and migrations from functional requirements.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/mdnaimul22/human-skills --skill database-schema-designer-mdnaimul22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-schema-designer
Source: https://github.com/mdnaimul22/human-skills/tree/main/skills/database-schema-designer
Command: npx skills add https://github.com/mdnaimul22/human-skills --skill database-schema-designer-mdnaimul22

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you turn product requirements into a well-structured relational database design, including relationships, constraints, indexing strategy, multi-tenancy enforcement, and migration-ready artifacts.

Core Features & Use Cases

  • Schema design from requirements: Extracts entities, defines relationships, and adds cross-cutting concerns like soft deletes, audit trails, and optimistic locking.
  • Migration and implementation outputs: Generates migration plans and supports common stacks such as Prisma, Drizzle, TypeORM, and Alembic patterns.
  • Operational rigor: Produces RLS policies for tenant isolation and recommends indexing (including partial indexes for active records).
  • Docs and visual planning: Creates ERD diagrams (Mermaid) and provides full schema examples you can adapt.

Quick Start

Ask the AI to design a multi-tenant PostgreSQL schema for your app’s requirements and include RLS policies, migration steps, and an ERD in Mermaid format.

Frequently Asked Questions about database-schema-designer

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

FAQPage Schema
How do I design a multi-tenant database schema with row-level security?

Design a multi-tenant database schema by extracting entities from requirements and applying RLS policy logic for tenant isolation. The schema includes table structures, constraints, and indexes to enforce secure data separation.

What is the best way to model relational database entities with soft deletes and audit trails?

Model relational database entities by defining relationships and adding cross-cutting concerns like soft deletes, audit trails, and optimistic locking. This approach produces normalized table structures reflecting necessary constraints and versioning.

Can I generate database migrations for Prisma or Drizzle from functional requirements?

Generate migration-ready artifacts for common stacks including Prisma, Drizzle, TypeORM, and Alembic patterns. The process creates migration plans and typed outputs directly from your extracted entity models.

How do I create an ERD diagram in Mermaid format for a PostgreSQL schema?

Create an ERD diagram in Mermaid format by extracting entities and relationships from your functional requirements. The output provides visual planning documentation alongside the generated table structures and indexes.

Does database schema design include indexing strategies for active records?

Database schema design includes indexing strategies by recommending partial indexes for active records. This ensures performance considerations are reflected directly within the normalized schema structure.

What are the limitations of designing a database schema from functional requirements?

Designing a database schema from functional requirements focuses on relational structures, multi-tenancy, and migrations. It does not handle non-relational databases, as it specifically produces table structures, RLS policies, and ERD generation.