medallion-architecture-design

Designs bronze, silver, and gold lakehouse layers with promotion gates and read-path enforcement.

1|Updated Jul 3, 2026
One-click install
npx skills add https://github.com/Nandansai08/skillz --skill medallion-architecture-design-nandansai08
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: medallion-architecture-design
Source: https://github.com/Nandansai08/skillz/tree/main/skills/data-analytics/medallion-architecture-design
Command: npx skills add https://github.com/Nandansai08/skillz --skill medallion-architecture-design-nandansai08

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Data platforms that grow organically end up with dashboards reading raw tables, multiple conflicting definitions of the same entity, and no way to reprocess data when logic bugs are found. This Skill provides a structured workflow for designing medallion (bronze/silver/gold) architectures where each layer has one job, promotion between layers is gated by executable tests, and reprocessing from raw data is a drilled capability rather than a hope. ## Core Features & Use Cases - Layer Contract Definition: Assigns each layer a single responsibility — bronze preserves raw data immutably, silver conforms and deduplicates entities, gold serves consumption-shaped marts — with written schema and quality contracts per layer. - Executable Promotion Gates: Encodes bronze-to-silver and silver-to-gold rules as blocking dbt tests, Delta constraints, or expectations suites, including quarantine tables with per-batch reconciliation (bronze = silver + quarantine). - Read-Path Enforcement and Reprocessing: Restricts layer access through warehouse grants rather than policy documents, and requires a staging rebuild drill to prove silver/gold can be reconstructed from bronze before it is needed. - Use Case: A scale-up with 400 dbt models and three conflicting definitions of orders uses this workflow to consolidate into 9 conformed silver entities, apply SCD2 only where analytically justified, and later replays 90 days of bronze in an afternoon when a currency bug is found in silver logic. ## Quick Start Use the medallion architecture skill to design the bronze, silver, and gold layers for our Databricks lakehouse, including promotion gates and ownership for each layer.

Frequently Asked Questions about medallion-architecture-design

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

FAQPage Schema
How do I design a medallion architecture for a lakehouse?▼

Assign each layer one job: bronze preserves raw append-only data with lineage columns, silver conforms and deduplicates entities at a defined grain, and gold serves consumption-shaped marts. Then encode promotion rules between layers as blocking dbt tests or constraints, and enforce read paths with warehouse grants.

What is the difference between bronze, silver, and gold data layers?▼

Bronze preserves raw as-received data immutably with no business logic, serving as the replay source. Silver cleans, types, deduplicates, and conforms one table per business entity. Gold holds consumption-shaped aggregates, marts, and feature tables, and may be duplicated per consumer by design.

Where should business logic live in a medallion architecture?▼

Logic that makes data correct — dedupe, typing, enum unification — belongs in silver. Logic that makes data useful for a purpose — fiscal calendars, attribution rules, KPI formulas — belongs in gold. Two consumers needing different definitions get two gold tables, never a forked silver table.

Does medallion architecture work with dbt and Snowflake?▼

Yes, the workflow applies to Databricks, Snowflake, and BigQuery with dbt. Promotion gates are implemented as dbt tests, Delta constraints, or expectations suites that block promotion on failure, and layer isolation is enforced through warehouse grants.

When should I use SCD2 vs SCD1 for slowly changing dimensions?▼

Decide per entity at the silver layer based on analytical need. Use SCD2 for entities whose past states matter, such as customer plan tier for revenue restatement, and SCD1 for correction-only attributes. SCD2 everywhere triples storage and join complexity.

When is medallion architecture the wrong approach?▼

This Skill does not cover per-run pipeline semantics like idempotency or retry behavior — that belongs to pipeline-level design. Three layers is the default, not a law; landing zones for CDC staging can earn their place, but extra silver-2 or silver-3 layers indicate unenforced boundaries.