> 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/categorize-icons.md).

# Categorize icons

The in-app categories help people find the icons they need quicker. Some icons are categorized automatically with a prefix in the name like `calendar_` or `folder_`, which works for icons like those. However, to give all names the prefix of games\_ for example, would add an unwanted attribute to the name.

That's why certain categories are curated by hand:

* Games
* System apps 

You can help by expanding these categories, it's even pretty easy to do, with no coding or creating skills required.

1. The categories are located inside `generated/`, there you will find `games.xml` & `system.xml`.
2. Click on one of the files and then on the edit button.
3. Add the names of the icons to the list (in alphabetical order). 
   1. You can easily search for icons using our search site.
4. Click commit changes, add a small description and create the pull request.

Please let us know if you would like to see more categories by creating a [GitHub issue](https://github.com/Arcticons-Team/Arcticons/issues/new).


---

# 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/categorize-icons.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.