Individual skill

multi-tenant-data-partitioner

Architects database multi-tenancy models (Shared DB/Schema vs Separate Schema vs Separate Database) and tenant routing.

skills/architecture/multi-tenant-data-partitioner/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 27
Repository last updated: Aug 20, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

claude-code Repository topic
ai Repository topic
ai-agents Repository topic
ai-coding Repository topic
ai-skill Repository topic
ai-skill-enhancement Repository topic
ai-skills Repository topic
ai-skills-analysis Repository topic
ai-skills-fest Repository topic
ai-skills-manager Repository topic
data Derived category
data-databases Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

README.mddoc · 612 bytes
SKILL.mdcore · 1,991 bytes
examples/example.mddoc · 866 bytes

Read excerpt


## Purpose

Architect secure, cost-effective, and scalable database multi-tenancy models (Shared Database/Shared Schema with Row-Level Security, Database-per-Tenant, Schema-per-Tenant) tailored to compliance, isolation, and cost constraints.

## When to Use

- Designing the data architecture for a B2B SaaS application.
- Enterprise customers requesting strict physical data isolation or custom backup schedules.
- Evaluating database costs vs cross-tenant data leakage risks.

## What to Analyze

1. **Isolation Model Selection**:
   - *Shared Database, Shared Schema (Pool)*: Highest resource efficiency, lowest cost, enforced via Postgres RLS.