> For the complete documentation index, see [llms.txt](https://docs.openbrim.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrim.org/examples/readme.md).

# Examples

Step-by-step example projects demonstrating OpenBrIM workflows for different bridge types. Each example walks through the complete process from geometry definition to analysis and design.

## Available Examples

| Example                         | Description                                              |
| ------------------------------- | -------------------------------------------------------- |
| **Steel I Girder Bridge**       | Complete workflow for a multi-span steel I girder bridge |
| **Steel Tub Girder Bridge**     | Curved steel tub girder bridge with complex geometry     |
| **Prestressed I Girder Bridge** | Precast prestressed concrete I girder bridge             |
| **Concrete U Girder Bridge**    | Post-tensioned concrete U girder bridge                  |

{% hint style="info" %}
Each example includes detailed input values and explanations to help you understand how to model similar structures in your own projects.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openbrim.org/examples/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
