> 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/data-display/kpicard.prompt.md).

# KpiCard.prompt

The dashboard metric tile — four to six of these in an `auto-fit` grid open every role dashboard.

```jsx
<div style={{ display: 'grid', gridTemplateColumns: 'repeat(auto-fit, minmax(220px, 1fr))', gap: 16 }}>
  <KpiCard icon="users" value="1,284" label="Total Students" color="blue" link="/reception/students" />
  <KpiCard icon="dollar" value="UGX 18.4M" label="Fees Collected" color="amber" />
  <KpiCard icon="whatsapp" value="1,102" label="WhatsApp Linked" color="green" />
</div>
```

### Props

* `icon` — glyph keys share aliases: `classes`/`door`, `exam`/`calendar`, `whatsapp`/`message`, `book`/`library`, `bell`/`notice`, `dollar`/`money`, `check`/`tasks`. Unknown keys render an info circle.
* `value` — defaults to an em dash; that is the deliberate pre-sync empty state, so leave it rather than showing `0`.
* `color` — tints the 44px icon chip only (10% fill, solid stroke). The value is always `--d-dark`.
* `link` — makes the tile an anchor; hover then lifts it 1px.

Money is written `UGX 18.4M` — currency code first, no symbol.


---

# 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/data-display/kpicard.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.