shard

Solid

Designing multi-tenant architectures with tenant isolation strategies, RLS, routing, and scale design for SaaS. Use when designing multi-tenant SaaS systems or tenant isolation.

AI & Automation 76 stars 13 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
63
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

<!-- CAPABILITIES_SUMMARY: - isolation_strategy: Design tenant isolation (database-per-tenant, schema-per-tenant, row-level) - rls_design: Design Row Level Security policies and tenant context propagation - tenant_routing: Design tenant routing (subdomain, header, path, JWT claim) - noisy_neighbor: Design resource limits, rate limiting, and fair scheduling per tenant - onboarding_flow: Design tenant provisioning and onboarding automation - migration_strategy: Plan single-tenant to multi-tenant migration paths - billing_metering: Design tenant usage metering and billing integration points - data_leak_assessment: Evaluate cross-tenant data leakage risks and design guardrails COLLABORATION_PATTERNS: - Schema -> Shard: DB schema feeds tenant isolation design - Gateway -> Shard: API design feeds tenant routing - User -> Shard: Requirements and constraints - Shard -> Schema: RLS policies and partition design for implementation - Shard -> Scaffold: Tenant-aware infrastructure configuration - Shard -> Builder: Implementation specifications - Shard -> Sentinel: Cross-tenant security verification BIDIRECTIONAL_PARTNERS: - INPUT: Schema (DB design), Gateway (API design), User (requirements), Atlas (architecture) - OUTPUT: Schema (RLS implementation), Scaffold (infra), Builder (implementation), Sentinel (security review) PROJECT_AFFINITY: Game(L) SaaS(H) E-commerce(M) Dashboard(M) Marketing(L) --> # Shard Design multi-tenant architectures. Shard turns SaaS requirements into tenant i...

Details

Author
simota
Repository
simota/agent-skills
Created
8 months ago
Last Updated
1 weeks ago
Language
HTML
License
MIT

Integrates with

Anthropic · AI

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

multi-tenancy

Isolate tenants in data, code, and capacity, choosing the right isolation model per tier. Use when designing SaaS data models or containing noisy-neighbor and cross-tenant risks.

7 Updated 5 days ago
Amey-Thakur
AI & Automation Listed

multitenancy

Multi-tenant architecture patterns. Database-per-tenant, schema-per-tenant, shared-schema with tenant ID, row-level security, tenant resolution, and data isolation. USE WHEN: user mentions "multi-tenant", "multitenancy", "SaaS architecture", "tenant isolation", "row-level security", "tenant ID", "subdomain routing" DO NOT USE FOR: general database design - use database skills; authentication - use auth skills

33 Updated today
claude-dev-suite
AI & Automation Listed

tenant-isolation

Design tenant isolation for a multi-tenant agentic product so one customer can never read, retrieve, remember, or be billed for another's data. Covers the three isolation models (pooled + row-level, bridge, silo), the agent-specific leakage paths most teams miss (cross-tenant retrieval, memory, cache, trace, and model-supplied tenant_id), where tenant_id binds into the Agent Contract / permissions / memory / tools / evals, and the mandatory cross-tenant leakage eval. Use whenever the user mentions multi-tenant, multi-tenancy, tenant isolation, B2B SaaS agent, per-customer data, row-level security / RLS, data residency, "can tenant A see tenant B's data," noisy neighbor, or namespacing memory/knowledge per customer.

14 Updated 1 months ago
Moai-Team-LLC