migrate-database

Generate standardized ORM database models with tenant isolation and UUID keys.

Updated Jan 10, 2026
One-click install
npx skills add https://github.com/dain-agency/mood-tracker --skill migrate-database
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-database
Source: https://github.com/dain-agency/mood-tracker/tree/main/.claude/skills/migrate-database
Command: npx skills add https://github.com/dain-agency/mood-tracker --skill migrate-database

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the repetitive manual work of writing boilerplate ORM model code for new database domains, ensuring every model adheres to your team's standards for tenant isolation, timestamp tracking, and UUID primary keys, reducing development errors and speeding up feature delivery.

Core Features & Use Cases

  • Tenant Isolation Enforcement: Automatically includes the required tenant_id field in all domain models to support multi-tenant application architectures.
  • Standardized Field Templates: Pre-configures UUID primary keys, created_at/updated_at timestamps, and created_by fields following your team's naming and default value conventions.
  • Registry Integration: Automatically registers new models in the tenant-scoped models registry to ensure they are properly recognized by your application's data layer.
  • Use Case: For example, when building a new customer support feature for your multi-tenant SaaS product, use this Skill to quickly generate compliant ticket and comment models that follow your organization's database standards without writing repetitive boilerplate code.

Quick Start

Use the migrate-database skill to add ORM models for the new "billing" schema namespace.

Frequently Asked Questions about migrate-database

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

FAQPage Schema
How do I generate ORM models with tenant isolation for a new database schema?

Generate ORM models with tenant isolation by automating the creation of standardized domain schemas that automatically include mandatory tenant_id fields, UUID primary keys, and timestamp tracking to support multi-tenant application architectures.

What fields are included in standardized multi-tenant ORM models?

Standardized multi-tenant ORM models include mandatory tenant_id fields for tenant isolation, UUID primary keys, created_at and updated_at timestamps, and created_by fields following snake_case naming conventions and default value standards.

How do I add a new domain schema to a tenant-scoped model registry?

Add a new domain schema to a tenant-scoped model registry by generating ORM models that automatically register new domains in your application's data layer, ensuring proper recognition and compliance with organizational database standards.

Can I use this for multi-tenant SaaS application database migration?

Use this for multi-tenant SaaS application database migration to enforce consistent tenant isolation, apply snake_case naming conventions, and eliminate repetitive manual boilerplate ORM code writing for new domain schemas.

Does this ORM model generation enforce snake_case naming conventions?

ORM model generation enforces snake_case naming conventions across all generated domain models, satisfying organizational database standards alongside mandatory tenant_id fields and tenant-scoped model registry registration.

What is the best way to automate boilerplate ORM code for multi-tenant domains?

Automate boilerplate ORM code for multi-tenant domains by generating standardized models that pre-configure tenant isolation, timestamp tracking, and UUID primary keys, reducing development errors and speeding up feature delivery.