> 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/steel-bridge-examples/example-steel-tub-girder-bridge-ex1-stg/templates-for-code-check-ex1-stg.md).

# Templates for Code Check

This section defines code check templates for efficient configuration of code check parameters.

{% hint style="info" %}
**Navigation:** Templates for Code Check
{% endhint %}

## Overview

Code check templates are created to collect frequently used settings by code check objects, which includes load combination tables, state specification preferences, analysis results, and AASHTO capacity computation settings for various bridge components.

### Supported Code Check Templates

* Steel Tub Girder Code Check Template
* Cross Frame Code Check Template
* Lateral Bracing Code Check Template
* Field Splice Code Check Template
* Pier Cap Code Check Template
* Pier Code Check Template
* Footing Code Check Template
* Pile Code Check Template

## Benefits

Templates allow you to:

* Define code check settings once and reuse across multiple elements
* Ensure consistency in code check configurations
* Reduce repetitive data entry

{% hint style="success" %}
Create templates before performing code checks to streamline the workflow.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.openbrim.org/examples/steel-bridge-examples/example-steel-tub-girder-bridge-ex1-stg/templates-for-code-check-ex1-stg.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.