@lightdash/cli 1.14.0 → 1.16.0

package/dist/vendor/template/references/chart-references.md

@@ -34,10 +34,10 @@ Each file contains:
 
 **How to use these:**
 1. Read the JSON file(s) to understand what data the user wants in their app
-2. Cross-reference the field IDs against the dbt YAML catalog at
-   `/tmp/dbt-repo/models/schema.yml` for field descriptions, types, and relationships
-   between fields — this helps you understand how the referenced charts connect to the
-   user's overall prompt
+2. Cross-reference the field IDs against the dbt YAML catalog — read
+   `/tmp/dbt-repo/models/<exploreName>.yml` for the referenced explores — for field
+   descriptions, types, and relationships between fields; this helps you understand how
+   the referenced charts connect to the user's overall prompt
 3. Map fields to SDK calls:
    - `chartName` → `query(exploreName).label(chartName)` — **always set the label**
    - `metricQuery.dimensions` → `.dimensions([...])`

package/dist/vendor/template/skill.md

@@ -49,7 +49,17 @@ Available at `@/components/ui/<name>`:
 
 ## Semantic Layer (dbt models)
 
-The available data models are defined in dbt YAML files at **`/tmp/dbt-repo/models/`**. Read these to discover every model, dimension, metric, join, and parameter available to you. **Never guess field names** — use only what's in the YAML. When a dimension or metric has `ai_hints`, follow that guidance when deciding which field best matches the user's intent; hints supplement names, labels, and descriptions. (Parameters live in a `parameters:` block under `meta:` / `config.meta:`, or in `lightdash.config.yml` — see [Parameters](#parameters).)
+The available data models are defined in dbt YAML files at **`/tmp/dbt-repo/models/`** — one file per model, plus an index. **Never guess field names** — use only what's in the YAML. When a dimension or metric has `ai_hints`, follow that guidance when deciding which field best matches the user's intent; hints supplement names, labels, and descriptions. (Parameters live in a `parameters:` block under `meta:` / `config.meta:`, or in `lightdash.config.yml` — see [Parameters](#parameters).)
+
+### Finding the right models
+
+Projects range from a handful of models to well over a thousand, so the directory is indexed rather than inlined:
+
+1. **Read `/tmp/dbt-repo/models/_index.md` first.** It lists every model, most-queried first, with its file name, dimension/metric counts, joined tables, and description.
+2. **Read only the model files the app actually needs**, e.g. `Read /tmp/dbt-repo/models/orders.yml`. Each file holds that model's complete dimensions, metrics, joins, and parameters.
+3. **Grep when the index isn't enough.** If you know a field name but not its model, `Grep` the directory for it. A wide model may be split across `<name>.yml`, `<name>.part2.yml`, … — the last line of each part points at the next.
+
+**Never read every model file, and never page through a file with `offset`/`limit`** — pick the model from the index and read that one file whole.
 
 ### Reading dbt YAML
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lightdash/cli",
-  "version": "1.14.0",
+  "version": "1.16.0",
   "description": "Lightdash CLI tool",
   "license": "MIT",
   "repository": {
@@ -41,8 +41,8 @@
     "unique-names-generator": "4.7.1",
     "uuid": "11.1.1",
     "yaml": "2.8.3",
-    "@lightdash/common": "1.14.0",
-    "@lightdash/warehouses": "1.14.0"
+    "@lightdash/common": "1.16.0",
+    "@lightdash/warehouses": "1.16.0"
   },
   "devDependencies": {
     "@types/inquirer": "8.2.4",