> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rixxui.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Core components

> Reference for the first-party rixx.core@0.1 component catalog.

`coreRUIConfig` includes the `rixx.core@0.1` catalog and trusted
implementations. All props use closed schemas, every component also supports a
dynamic `visible` value, and graph/resource budgets apply.

## Answer and content

| Component      | Purpose                                                 |
| -------------- | ------------------------------------------------------- |
| `Answer`       | Root for one immutable assistant answer                 |
| `Heading`      | Semantic level 1-6 heading                              |
| `Text`         | Constrained plain text                                  |
| `RichText`     | Plain or sanitized Markdown text                        |
| `CodeBlock`    | Highlighted, copyable code with language/title metadata |
| `Quote`        | Quotation with optional attribution                     |
| `List`         | Ordered or unordered identified text items              |
| `Steps`        | Sequential steps with optional status                   |
| `Citation`     | One source reference with optional safe URL             |
| `CitationList` | Numbered source collection                              |
| `Math`         | Accessible KaTeX inline or display expression           |
| `Badge`        | Compact semantic label                                  |

## Layout and feedback

| Component    | Purpose                                               |
| ------------ | ----------------------------------------------------- |
| `Stack`      | Row or column layout                                  |
| `Grid`       | Responsive peer-content grid                          |
| `Card`       | Grouped content surface                               |
| `Section`    | Semantic answer section                               |
| `Tabs`       | Keyboard-accessible local tabs                        |
| `Accordion`  | Local disclosure group                                |
| `Each`       | Repeat one child template over bound data             |
| `Alert`      | Concise status message                                |
| `Callout`    | Highlighted note, warning, insight, or recommendation |
| `EmptyState` | Empty-result fallback with optional action            |
| `StateView`  | Select loading, error, or content child               |
| `Progress`   | Labeled completion/status progress                    |

## Data

| Component   | Purpose                                                   |
| ----------- | --------------------------------------------------------- |
| `Metric`    | Primary formatted value with optional change              |
| `KeyValue`  | Compact labeled facts                                     |
| `Timeline`  | Chronological identified events                           |
| `DataTable` | Filterable, sortable, paginated responsive records        |
| `Chart`     | Ten chart kinds with optional legend and accessible table |
| `Diagram`   | Sanitized committed Mermaid diagram                       |

## Input and media

| Component   | Purpose                                                      |
| ----------- | ------------------------------------------------------------ |
| `Button`    | User-initiated registered action                             |
| `Form`      | Local named fields that emit one action payload              |
| `TextField` | Labeled single-line input with rules                         |
| `Select`    | Labeled single-choice input                                  |
| `Image`     | Policy-governed responsive HTTPS image                       |
| `Gallery`   | Grid/carousel/justified image collection and media viewer    |
| `Icon`      | Vetted semantic icon                                         |
| `BrandLogo` | Neutral domain monogram, not an official fetched brand asset |

Detailed property schemas are available at runtime through
`coreRUIConfig.catalog.components` and in generated instructions. Prefer those
machine-readable contracts over duplicating schema definitions in host prompts.