> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paradime.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure data pipelines

> Use DinoAI to update your dbt_project.yml so models map to your folder structure with the right materializations, schemas, and tags.

DinoAI can analyze your project structure and update your `dbt_project.yml` with sensible materializations, schema naming, and tags. In this guide you update your project configuration to match your folder structure.

<Note>
  **Prerequisites**

  * DinoAI copilot access in your Paradime workspace.
  * A dbt™ project with a `dbt_project.yml` file and an organized folder structure.

  Estimated time: 5 minutes.
</Note>

## Steps

<Steps>
  <Step title="Add your dbt_project.yml as context">
    In DinoAI, click the "@" symbol and add your existing `dbt_project.yml` so DinoAI preserves your custom settings while adding new configuration.
  </Step>

  <Step title="Enter your prompt">
    Describe the configuration you want. For example:

    > Can you update my dbt\_project.yml to map all my models to my folder structure so each SQL file writes to the respective schema, and make sure they are tagged?

    DinoAI analyzes your folder structure and existing configuration, identifies model types based on folder organization (staging, intermediate, marts, and so on), and generates configuration sections with schema naming and materializations. If configured, it applies your [.dinorules](/guides/dinoai-copilot-use-cases/using-your-project-as-context-to-set-up-.dinorules) preferences.
  </Step>

  <Step title="Review the generated configuration">
    Review the proposed changes before accepting them. The output maps each folder to a materialization, schema, and set of tags.

    ```yaml theme={"system"}
    # dbt_project.yml update

    models:
      formula_one:
        +materialized: view
        +schema: "{{ target.schema }}"

        source:
          +schema: "{{ target.schema }}_source"
          +tags: ["source", "formula_one"]

        staging:
          +schema: "{{ target.schema }}_staging"
          +tags: ["staging", "formula_one"]
          f1:
            +tags: ["f1"]

        intermediate:
          +schema: "{{ target.schema }}_intermediate"
          +tags: ["intermediate", "formula_one"]

        marts:
          +materialized: table
          +schema: "{{ target.schema }}_marts"
          +tags: ["marts", "formula_one", "reporting"]
          f1:
            +tags: ["f1"]
    ```
  </Step>

  <Step title="Accept and build">
    Accept the changes, then run a build to confirm models write to the expected schemas with the right materializations.
  </Step>
</Steps>

<Check>
  Your `dbt_project.yml` maps each folder to the correct materialization, schema, and tags, and a build writes models to the expected schemas. If a model lands in the wrong schema, check that its folder matches a configured section.
</Check>

## Next steps

<CardGroup cols={2}>
  <Card title="Generate documentation" href="/guides/dinoai-copilot-use-cases/generating-documentation" icon="book">
    Add model and column descriptions with tests.
  </Card>

  <Card title="Build marts models" href="/guides/dinoai-copilot-use-cases/building-marts-models" icon="table">
    Combine multiple models with business logic.
  </Card>

  <Card title="DinoAI use cases" href="/guides/dinoai-copilot-use-cases/index" icon="sparkles">
    Explore more ways to work with DinoAI.
  </Card>

  <Card title="Copilot reference" href="/products/dino-ai/copilot/index" icon="bot">
    How context and Agent Mode work.
  </Card>
</CardGroup>


## Related topics

- [Build marts models](/guides/dinoai-copilot-use-cases/building-marts-models.md)
- [Generate documentation](/guides/dinoai-copilot-use-cases/generating-documentation.md)
- [Workspaces and data mesh](/guides/paradime-fundamentals/workspaces-and-data-mesh.md)
- [Orchestrate data pipelines](/guides/ship-to-production/index.md)
- [Bolt Pipelines](/products/bolt/index.md)