> For the complete documentation index, see [llms.txt](https://klassdocs.gitbook.io/klassapp-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://klassdocs.gitbook.io/klassapp-documentation/design/system/components/core/icon.prompt.md).

# Icon.prompt

A Heroicons v1 outline glyph stroked in `currentColor` — use it for every icon in app chrome.

```jsx
<Icon name="users" size={20} />
<Icon name="chevronDown" size={16} style={{ color: 'var(--d-muted)' }} />
```

**Intentional addition.** The source design system carries icon paths inline inside `KpiCard` and nowhere else; this wrapper exposes the same family (Heroicons v1 outline, 24×24, stroke 2) so sidebars and toolbars don't need hand-drawn SVG. The eight KpiCard glyphs are byte-identical to the source; the chrome glyphs (home, document, upload, logout, search, plus, menu, close, chevrons, tick) are their Heroicons v1 siblings.

### Rules

* Stroke weight is always 2; never fill an icon.
* Icons inherit text colour. Tint by setting `color` on the parent, not by hardcoding a hex.
* Icons are decorative by default (`aria-hidden`). Pass `title` only for icon-only buttons.
* No emoji in product chrome. Emoji do appear inside the Toshi assistant's plan/step cards (`.toshi-plan-step-icon`) — that is the one sanctioned exception.


---

# 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://klassdocs.gitbook.io/klassapp-documentation/design/system/components/core/icon.prompt.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.