> For the complete documentation index, see [llms.txt](https://lanefox.gitbook.io/attributes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lanefox.gitbook.io/attributes/design/design-structure.md).

# Design - Structure

Getting Attributes onto an Agent is easy.

#### Relevant Components

`AgentAttributes`, `AgentVitals`, `AttributePreset`,  

#### Typical Setup

1. Create an `AttributePreset` in the Vault Dashboard. Configure it as you wish.
2. Add `AgentAttributes` and `AgentVitals` components to a GameObject. 
3. Point the `AgentAttributes` to the `AttributePreset` you've made in the Vault.
4. Profit.

#### Scenario A (ideal)

Structure :

* Scene GameObject "Player Bob" (`YourPlayerClass`)(`AgentAttributes`) (`AgentVitals`) where `YourPlayerClass` implements `IAttributeUser.`

That's it, you're done. If you're using Mirror then the complier directives will automatically enable the networking code for `AgentVitals.cs` (incomplete feature as of 2/2021). Just make sure you properly interact with the server/client in your own code. 

Refer to the the **In Concept** and **In Practice** page for more information.


---

# 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://lanefox.gitbook.io/attributes/design/design-structure.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.