stg_ naming convention

Staging directory structure

Source YAML file naming

Model YAML file naming

Source freshness config

Source column tests

CTE pattern

source() macro used

Column renaming — id to entity_id

Column renaming — _loaded_at

Lowercase string fields

Cents-to-dollars conversion

Model YAML documentation

int_ prefix naming

fct_ prefix naming

Directory structure

ref() macro used

Incremental materialization

unique_key specified

Merge strategy for updates

merge_update_columns

is_incremental() filter

Filter uses max(updated_at)

Intermediate uses CTE structure

on_schema_change config

Layer materializations

Schema assignments

vars for start date

generate_schema_name macro

limit_data_in_dev macro

DRY utility macro

dim_ prefix naming

Surrogate key

_loaded_at metadata

ref() macro used

dbt_utils tests

packages.yml

Model YAML documentation

accepted_values test

expression_is_true test

recency test on fact table

relationships test in model YAML

Primary key tests — unique + not_null

packages.yml with dbt_utils

Model-level descriptions

Column-level descriptions

Model YAML naming

not_null on numeric measures

Test coverage on both dim and fct

insert_overwrite strategy

partition_by config

Derived date partition column

is_incremental() filter with lookback

fct_ prefix naming

incremental materialization

ref() macro usage

Correct directory placement

CTE structure

_loaded_at metadata

No unique_key for insert_overwrite

var() usage in model SQL

No hardcoded dates in models

limit_data_in_dev used in model

limit_data_in_dev macro defined

vars declared in dbt_project.yml

generate_schema_name macro

Layer materializations in dbt_project.yml

Staging uses view materialization

Model references use ref()

dbt build mentioned in workflow

Separate dev and prod targets described