> For the complete documentation index, see [llms.txt](https://docs.arcticons.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcticons.com/contribute/credit-yourself.md).

# Credit Yourself

Give yourself an entry at the bottom of `generated/contributors.xml` to be included in the credits!

Just add this before the `</resources>` tag and edit the values

```
<contributor
    name="Contributor Name"
    contribution="Icon Creator."
    image="assets://contributors/yourImageName.png"
    link="https://linktoyourpage" />
```

For the name parameter enter your name or username

For the contribution parameter write what you have contributed (Icon Creator)

For the image you have multiple options&#x20;

* leave it empty `""`
* add a Link to your picture `"https://linktoyourpicture"`
* save your image in `app/src/main/assets/contributors/` and  link to it with `"assets://contributors/'yourImageName.png'"`

For the link parameter you can set the link to your GitHub profile or your website.


---

# 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.arcticons.com/contribute/credit-yourself.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.