# Glossary

### <mark style="color:red;">Akinon UI</mark>

**Akinon UI**: The umbrella term for all UI technologies and components used in the Akinon ecosystem. Encompasses UI Kit, UI Protocol, and application layers.

**UI Protocol**: The set of standards, technical rules, and integration methods that define how UI Kit, Shell App, Client App, and plugin/fullpage concepts work together. It is the architectural and documentation backbone for modern Akinon frontend projects.

**UI Kit**: The reusable UI component library developed by Akinon and published on npm. Used for design consistency and rapid development. UI Kit is a part of the UI Protocol.

**Differences**: UI Kit is just the component set; UI Protocol defines how components, apps, and integrations work together. Akinon UI is the umbrella for all these layers.

***

### <mark style="color:red;">Application Types & Concepts</mark>

**Shell App**: The main host application that contains and orchestrates other apps, plugins, and pages. Manages navigation, layout, and micro-frontend integration. Central to the UI Protocol architecture.

**Client App**: An independent app running inside the Shell App, usually providing a specific business function or page.

**Fullpage**: A client app rendered as a full viewport page within the Shell App, typically representing a standalone workflow or application.

**Plugin**: A small, independent app or component rendered in a specific area (e.g., panel, widget, sidebar) of the Shell App. Unlike fullpage, it does not take over the entire screen.

**Hybrid App**: A client app that can function as both a fullpage and a plugin, adapting to different roles as needed. Enables flexible integration in the UI Protocol architecture.

***

### <mark style="color:red;">Components & Features</mark>

**AI Spinner**: A UI component that displays a loading spinner with AI-related styling or behavior, used to indicate ongoing AI-driven processes.

***

*If you encounter a term not listed here, please refer to the relevant npm package documentation or contact the maintainers for clarification.*


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.akinon.com/akinon-ui/resources/glossary.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.