feat: add full-project build rule and common pitfalls to builder prompt and skills

- Add principle 4 to builder prompt: "Fix everything" — run full `dbt build` after changes
- Add full project build instruction after first-build note
- Add 4 new common pitfalls: column casing, stopping at compile, skipping full build, ignoring pre-existing failures
- Add iron rule 5 to dbt-develop: fix ALL errors including pre-existing
- Expand dbt-troubleshoot iron rule to include fixing all errors, not just reported ones

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: suryaiyer95

.opencode/skills/dbt-develop/SKILL.md

@@ -122,6 +122,7 @@ Use `altimate-dbt children` and `altimate-dbt parents` to verify the DAG is inta
 2. **Never stop at compile.** Always `altimate-dbt build` to catch runtime errors.
 3. **Match existing patterns.** Read 2-3 existing models in the same directory before writing.
 4. **One model, one purpose.** A staging model should not contain business logic. An intermediate model should not be materialized as a table unless it has consumers.
+5. **Fix ALL errors, not just yours.** After creating/modifying models, run a full `dbt build`. If ANY model fails — even pre-existing ones you didn't touch — fix them. Your job is to leave the project in a fully working state.
 
 ## Common Mistakes
 

.opencode/skills/dbt-troubleshoot/SKILL.md

@@ -23,9 +23,10 @@ description: Debug dbt errors — compilation failures, runtime database errors,
 - Adding tests → use `dbt-test`
 - Analyzing change impact → use `dbt-analyze`
 
-## The Iron Rule
+## Iron Rules
 
-**Never modify a test to make it pass without understanding why it's failing.**
+1. **Never modify a test to make it pass without understanding why it's failing.**
+2. **Fix ALL errors, not just the reported one.** After fixing the specific issue, run a full `dbt build`. If other models fail — even ones not mentioned in the error report — fix them too. Your job is to leave the project in a fully working state. Never dismiss errors as "pre-existing" or "out of scope".
 
 ## Diagnostic Workflow
 

packages/opencode/src/altimate/prompts/builder.txt

@@ -5,6 +5,7 @@ You are altimate-code in builder mode — a data engineering agent specializing
 1. **Understand before writing** — Read existing code, schemas, and actual data before writing any SQL. Never write blind.
 2. **Follow conventions** — Match the project's naming patterns, layer structure, and style. Read 2-3 similar files first.
 3. **Validate the output** — A task isn't done until the output data looks right. Check row counts, sample values, and column names.
+4. **Fix everything** — After finishing your changes, run a full `dbt build` (no `--select`). If ANY model fails — even ones you didn't touch — fix it. Leave the project fully green.
 
 ## dbt Operations
 
@@ -21,6 +22,8 @@ altimate-dbt info                       # Project metadata
 
 **Before the first build**, if `packages.yml` exists but `dbt_packages/` does not, run `dbt deps` to install packages.
 
+**After finishing your model(s)**, run a full project build: `altimate-dbt build` (no `--model` flag). Fix every failure — even pre-existing ones.
+
 ## Workflow
 
 1. **Explore**: Read existing models, schemas, and sample data before writing anything.
@@ -34,3 +37,7 @@ altimate-dbt info                       # Project metadata
 - **Fan-out joins**: One-to-many joins inflate aggregates. Check grain before joining.
 - **Missing packages**: If `packages.yml` exists, run `dbt deps` before building
 - **NULL vs 0 confusion**: Do not add `coalesce(x, 0)` unless the task explicitly requires it. Preserve NULLs from source data.
+- **Column casing**: Many warehouses are case-insensitive but return UPPER-case column names. Always check actual column names with `altimate-dbt columns` before writing SQL.
+- **Stopping at compile**: `altimate-dbt compile` only checks Jinja syntax. Always follow up with `altimate-dbt build` to catch runtime SQL errors.
+- **Skipping full project build**: After your model works, run `altimate-dbt build` (no flags) to catch any failures across the whole project.
+- **Ignoring pre-existing failures**: If a model you didn't touch fails during full build, fix it anyway. The project must be fully green.