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

# Graphic Elements

Lines and the RAID gear pattern.

## Lines

Lines can run vertically or horizontally to divide and create space in documents.

* Keep lines either **thick** or **thin**, using these weights: **10 pt**, **2 pt** and **1 pt**.
* Lines should be **Raider Red** or **AI Yellow** only.

<figure><img src="https://3334852250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwm6OlhXV0nI2HIvnDxa8%2Fuploads%2Fgit-blob-93153360c49cbd40c5b49b11f28e79ff1df3b94c%2Fgraphic-lines.png?alt=media" alt="Line weights of 10, 2 and 1 point in AI Yellow and Raider Red" width="350"><figcaption><p>Line weights</p></figcaption></figure>

## Patterns

A single repeating gear pattern exists to use as a focal point when needed. Download it from [Graphics & Specialty Marks](https://docs.raidrobotics.org/brand/asset-library/graphics.md#gear-pattern).

<figure><img src="https://3334852250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwm6OlhXV0nI2HIvnDxa8%2Fuploads%2Fgit-blob-4a5508545951f373f048f7d87f84f1b951d17a3b%2Fgraphic-pattern.png?alt=media" alt="Repeating Raider Red gear outline pattern"><figcaption><p>Gear pattern</p></figcaption></figure>

{% hint style="danger" %}
Never distort the pattern, and never place text or imagery directly on top of it.
{% 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.raidrobotics.org/brand/brand-standards/graphic-elements.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.
