​

sqb playground

​

Usage

sqb playground [name]

​

Templates

​

What it creates

• Staging views, fact/dimension tables, and incremental models
• Sources with inline expression data (no external setup)
• Seeds, SQL functions, and a custom materialization
• Built-in and custom audits
• SQL unit tests including chain tests
• E2E scenario tests
• Python macros
• AI agent skill files (auto-installed for OpenCode, Claude Code, and other agents)

• dagster/definitions.py - Dagster definitions with sqlbuild_assets, sqlbuild_scenario_checks, and SqlBuildCliResource
• dagster/README.md - Setup instructions

• tasks/orders.py, loaders/orders.py, assets/orders_export.py, checks/orders_export.py
• A fact_orders SQL model over a managed raw_orders source
• Examples of the SQL boundary, ctx.relation(model(...)), soft-skip fan-in, and a Python check

​

Examples

# Default waffle shop
sqb playground waffle-shop
cd waffle-shop
sqb build

# With Dagster integration
sqb playground --template dagster
cd sqlbuild-playground
uv pip install 'sqlbuild[dagster]'
dagster dev -f dagster/definitions.py

# With Rivers integration
sqb playground --template rivers
cd sqlbuild-playground
uv pip install 'sqlbuild[rivers]'
uv run rivers dev rivers_pipeline.definitions

# With virtual environments
sqb playground --template virtual
cd sqlbuild-playground
sqb state init
sqb build
sqb build --virtual-env pr
sqb promote --from pr --to dev

# With Python nodes
sqb playground --template python_nodes
cd sqlbuild-playground
sqb build --select +fact_orders --select +orders_export
sqb check --select +check_orders_export

​

Notes

• The target directory must not already exist
• DuckDB is included as a core dependency - no extra installation needed
• The local DuckDB database file is created on the first build
• The Dagster template uses prepare_if_dev() to auto-generate the DAG artifact when Dagster starts in dev mode