data-model

Design multi-tenant database schemas with migrations and Go/TypeScript repositories.

2|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/ashtonian/llm-init --skill data-model-ashtonian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-model
Source: https://github.com/ashtonian/llm-init/tree/main/templates/.claude/skills/data-model
Command: npx skills add https://github.com/ashtonian/llm-init --skill data-model-ashtonian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing robust, scalable multi-tenant database schemas with consistent migrations and repository interfaces is time-consuming and error-prone without a repeatable blueprint.

Core Features & Use Cases

  • Entity-relationship modeling for tenants, users, projects, and tasks, with visual Mermaid diagrams for quick validation.
  • Multi-tenant table design including base fields, constraints, indexes, and row-level security scaffolding.
  • Auto-generated migrations & repositories in Go and TypeScript, plus in-memory test stubs to accelerate development.
  • Use Case: Rapidly bootstrap a SaaS feature with isolated tenant data and standardized data-access layers.

Quick Start

Design a multi-tenant schema for a new SaaS feature and generate migrations and repositories.

Frequently Asked Questions about data-model

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

FAQPage Schema
How do I design a multi-tenant database schema for a SaaS application?

Designing a multi-tenant database schema involves creating tables with standardized base columns, indexing, constraints, and row-level security scaffolding to ensure scalable tenant isolation for SaaS projects.

Can I auto-generate database migrations and repository layers for Go and TypeScript?

Yes, you can auto-generate database migrations and repository interfaces in Go and TypeScript, including in-memory test stubs, to accelerate data-access layer development for multi-tenant tables.

What is the best way to isolate tenant data in a PostgreSQL database?

The best way to isolate tenant data in PostgreSQL is by applying row-level security scaffolding alongside standardized base columns, constraints, and indexing within a structured multi-tenant schema design.

How do I model entity relationships for tenants, users, and projects with visual validation?

You can model entity relationships for tenants, users, projects, and tasks by generating visual Mermaid diagrams, allowing quick validation of multi-tenant database structures before implementation.

Does this approach support the repository pattern for multi-tenant data access?

Yes, the approach supports the repository pattern by generating standardized data-access repository layers in Go and TypeScript, providing a consistent interface for querying isolated multi-tenant data.

When do I need row-level security and standardized base columns in multi-tenant migrations?

You need row-level security and standardized base columns in multi-tenant migrations when building SaaS features that require strict tenant data isolation and consistent, scalable database schemas.