skills.rest
nguyenpv1980-wq
nguyenpv1980-wqCOMMUNITY
Explore all skills by this author →
GitHub

warehouse-lake-architect

Design warehouse, lake, or lakehouse architecture with governed zones and tenant isolation.

2|Updated Jul 6, 2026
Search Tags:#analytics#catalog#data modeling#warehouse#lakehouse#tenant isolation#pii governance
One-click install
npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill warehouse-lake-architect
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: warehouse-lake-architect
Source: https://github.com/nguyenpv1980-wq/Project-Aegis/tree/main/.claude/skills/warehouse-lake-architect
Command: npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill warehouse-lake-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill designs the analytical destination for a multi-tenant SaaS so reporting and analytics do not devolve into swamp-like lakes or undocumented view sprawl. It helps you choose the right estate class, define governed zones, and keep tenant isolation and PII rules intact as data moves into analytics.

Core Features & Use Cases

  • Estate Class Selection: Chooses warehouse, lake, or lakehouse based on workload shape, governance needs, and team maturity.
  • Zone and Mart Design: Defines raw, conformed, and curated zones with ownership, contracts, retention, and access rules.
  • Tenant-Safe Analytics: Preserves tenant keys through every zone and designs per-tenant access paths for customer-facing analytics.
  • Modeling and Layout Guidance: Recommends dimensional or wide modeling per mart, SCD policy, partitioning, formats, and compaction strategy.
  • Governed Adoption Path: Adds catalog registration, ingestion handoff boundaries, PII handling, and incremental migration from existing analytics sprawl.

Quick Start

Ask the Skill to design our analytical estate for a small SQL-heavy team, including zones, marts, tenant isolation, and the adoption path from our current analytics setup.

Frequently Asked Questions about warehouse-lake-architect

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

FAQPage Schema
How do I design a multi-tenant lakehouse architecture that preserves tenant isolation in analytics?▼

Design multi-tenant lakehouse analytics by choosing estate classes, defining governed raw and curated zones with contracts, and preserving tenant keys through every zone to maintain isolation. This prevents data sprawl while supporting finance reporting and customer-facing analytics.

What's the best way to choose between a data warehouse and a lakehouse for a SaaS analytics platform?▼

Choose between warehouse, lake, and lakehouse architectures by evaluating workload shape, governance maturity, and team SQL proficiency. Warehouse suits SQL-heavy teams, while lakehouses fit diverse BI, reporting, and data science workloads needing governed zone contracts.

How do I govern PII lifecycle and tenant access paths across data marts?▼

Govern PII lifecycle and tenant access by defining catalog fields, per-mart modeling choices, and tenant-safe access patterns. These preserve isolation and erasure feasibility as data moves through governed zones into curated marts.

When do I need zone contracts and catalog registration for my data warehouse?▼

Zone contracts and catalog registration are needed when migrating from undocumented view sprawl to a governed analytics estate. They establish ingestion handoff boundaries, ownership rules, and retention policies that prevent uncontrolled data swamp expansion.

Can I migrate incrementally from existing analytics sprawl to a governed lakehouse without downtime?▼

Incremental migration from analytics sprawl is supported through governed adoption paths that define ingestion handoff boundaries and catalog registration. This approach rationalizes existing warehouse sprawl while progressively establishing governed zones and marts.

How do I prevent data lake sprawl when building customer-facing analytics for multiple tenants?▼

Prevent data lake sprawl by specifying governed zones with explicit ownership, modeling choices, and partitioning strategies. Per-tenant access paths and tenant key preservation through every zone keep customer-facing analytics isolated and documented.

Related Skills

Explore More Data & Analytics Skills→
olafkfreundolafkfreund
9

COSMIC Desktop UI Design & Development Excellence

Standardize COSMIC UI design and development for desktop apps and applets.

Community
Basic
shafibabarshafibabar
1

data-model-design

Design normalized OLTP schemas and dimensional OLAP marts with PostgreSQL constraints.

Community
Advanced
mark64oswaldmark64oswald

Dimensional Modeling Skill

Design star and snowflake schemas with fact and dimension tables.

Community
Intermediate
weiflycc-cmdweiflycc-cmd

e2e-medallion-architecture

Implement end-to-end medallion architecture lakehouse patterns in Microsoft Fabric.

Community
Advanced