multi-tenant-data-architect

What problem does it solve?

This Skill helps you design how tenant data is stored, scoped, migrated, and protected across databases, caches, search indexes, vector stores, and other persistence layers in a multi-tenant system. It prevents ambiguous tenancy boundaries, unsafe client-supplied tenant context, and incomplete isolation designs that can lead to cross-tenant leakage.

Core Features & Use Cases

• Per-store scoping decisions: Choose and justify pooled, schema-per-tenant, database-per-tenant, or mixed strategies for each storage layer.
• Tenant-context propagation: Define how tenant identity is derived server-side and carried safely into queries and jobs.
• Ownership and lifecycle mapping: Classify data as tenant-owned, shared/reference, or platform, and plan suspend, offboard, and purge behavior across stores.
• Migration and isolation planning: Produce expand-backfill-verify-enforce-contract migration steps, rollback paths, and a data-layer isolation test matrix.
• Use case: A team adding Redis and search to an existing Postgres app can use this Skill to design tenant-safe scoping for all stores and plan a reversible retrofit.

Quick Start

Ask the skill to design tenant-scoped storage for your app, including per-store isolation choices, server-derived tenant context propagation, lifecycle handling, and a verified migration plan.