> For the complete documentation index, see [llms.txt](https://documentation.lynnux.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.lynnux.xyz/akira/automation/reactionroles/new.md).

# New

1. To create a new ReactionRoles message, respond to the first prompt with `new`.
2. You will then be asked to tag the channel your ReactionRole message will be in. Respond by tagging the channel.
3. Next, you'll be asked to provide a title and description for your ReactionRole message. Format your response like this: `title|description`
4. The next prompt will ask you to provide a color for the embed of your ReactionRole message. Respond with the name or hex code of a color.
5. You'll then be asked to list the roles and corresponding emotes that you wish to use in your ras message. Add them **one at a time** **in separate messages** using this format: `emoji role`
6. When you have finished adding roles, say `done`.
7. The final prompt will ask if you want the roles to be unique. If you want members to be able to choose multiple roles from the ras message, respond with `no`. Otherwise, respond with `yes`.

{% hint style="info" %}
If you need help finding a hex code, you may refer to [this site](https://htmlcolorcodes.com). Use the code next to the #.
{% 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://documentation.lynnux.xyz/akira/automation/reactionroles/new.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.