// Manage and enforce path templating and naming conventions in dbt-helpers. Use when implementing PathPolicy, defining template variables, or configuring warehouse-specific defaults.
Manage Architecture Decision Records (ADRs) using adr-tools. Use this to initialize, create, list, and link ADRs to document architectural evolution.
Scaffold and standardize new dbt-helpers plugins (Warehouse, Tool, or Schema). Use when starting a new plugin implementation or updating plugin discovery configuration.
Comprehensive workflow for creating, implementing, and validating Agent Skills. Use when asked to "create a new skill", "author a skill", "add a capability", or when standardizing project-specific workflows. Support for platform detection (Cursor, Claude Code, Gemini CLI, Codex) and template selection.
Set up the development environment for the project. Use when starting work on the project, when dependencies are out of sync, or to fix environment setup failures.
Implement and run End-to-End tests using golden output comparison. Use when verifying CLI behavior, plan generation, or full project execution.
Set up and run integration tests using Testcontainers. Use when testing warehouse adapters against real database engines or verifying filesystem-dependent operations.
| name | dbt-helpers-path-policy |
| description | Manage and enforce path templating and naming conventions in dbt-helpers. Use when implementing PathPolicy, defining template variables, or configuring warehouse-specific defaults. |
To ensure consistent and predictable file locations and resource names across different dbt projects and warehouses.
{{ variable }} (e.g., models/{{ dataset }}/{{ table }}.sql).Derived from CatalogRelation and CatalogNamespace:
project / databasedataset / schematable / identifierkind (table, view, etc.)namespace_0, namespace_1, ... (positional parts)dbt_helpers.yml.models/{{ project }}/{{ dataset }}/{{ kind }}/{{ table }}.sqlmodels/{{ schema }}/{{ table }}.sql