# kometa-ui > Angular 22 UI kit: standalone, OnPush, signal-based components with the `k-` selector prefix, themed > by CSS custom properties, light and dark. No PrimeNG, Material or Tailwind dependency. This guide is for AI coding agents building an app with `kometa-ui`. The per-component reference (selectors, inputs, outputs, types, defaults) is `components.md` next to this file, generated from the source. Live docs: https://inomjonismaylov.github.io/kometa-ui-kit/ (one page per component, `#button`, `#drawer`...). ## Setup (all three steps are required) `ng add kometa-ui` (0.3.0 and later) does all three: it installs the package, puts the two `@use` lines at the top of the global `.scss` stylesheet (or the two files first in `angular.json` `styles` for a CSS-only app) and adds `provideKometaUi()`. By hand: ```bash npm install kometa-ui ``` ```ts // app.config.ts import { provideKometaUi } from 'kometa-ui'; export const appConfig: ApplicationConfig = { providers: [provideKometaUi()] }; ``` ```scss // styles.scss: `layers` MUST be the first @use, or component styles lose to the app's. @use 'kometa-ui/styles/layers'; @use 'kometa-ui/styles/base'; // tokens, fonts and base primitives ``` Tailwind v4: also `@import 'kometa-ui/styles/kometa-theme.css';` to map the tokens to utilities. ## Using components - Import each class from its entry point, `kometa-ui/` (the file name without `kometa-`): `import { KometaButton } from 'kometa-ui/button'; import { KometaDrawer } from 'kometa-ui/drawer';`. `from 'kometa-ui'` re-exports them all and works, but it puts every kit component any lazy route uses into the app's initial chunk. then list them in the standalone component's `imports: [...]`. - Find the class for a selector in `components.md` (`button[k-button]` is `KometaButton`, `button[k-halo]` is `KometaHalo`). - Inputs are signal inputs: bind them with `[label]="x"` or a static `label="Save"`. Boolean inputs take a bare attribute: ``. - `model` inputs are two-way: ``, ``. - Forms: components marked "A Signal Forms control" in `components.md` bind with `[formField]="form.name"` (`@angular/forms/signals`); those marked "Works with Angular forms" take `formControl` / `formControlName` / `ngModel`. The rest bind through their `model`. - Buttons are native elements with the kit on them: ``, `Book`; use the DOM's own `type`, `disabled`, `aria-label`, `class` and `(click)`. `` is the deprecated wrapper (`KometaButtonElement`), kept for one minor release. - Other output names are the library's own, not DOM names: ``. Check `components.md` before guessing. - Read the component's doc comment in `components.md` (or its `.d.ts` in `node_modules/kometa-ui`) before using an input you have not seen; inputs are often unions like `'secondary' | 'danger' | null`. ## Services and app-wide pieces - Confirm dialogs: put exactly one `` in the root component, then `inject(KometaConfirmationService).confirm({ header, message, acceptLabel, rejectLabel, acceptButtonProps: { severity: 'danger' }, accept, reject })`. - Toasts: ``; you own the `KometaToastItem[]` list. - Theme: `inject(ThemeService).set('light' | 'dark' | 'system')`; it writes `data-theme` on ``. Without it the system preference wins, dark when the system says nothing. - `k-tabbar` tabs with `link` and `k-row` with `link` use the router, so the app needs `provideRouter(...)`. - Charts (`k-chart`, `k-bars`, `k-donut`, `k-spark`, `k-gauge`, `k-heat`) take plain data and a required `label` for screen readers, colour series from `--viz-1`…`--viz-5` (`chartColor(i)`), and play their entrance once when first on screen (`KometaInView`, `[kInView]`, which you can use on your own elements). Lay KPI tiles (`k-stat`) out in `k-tiles`, which never leaves one tile alone on a row. For a chart the kit lacks, draw it with the same maths from `kometa-ui/scale` (`niceScale`, `spread`, `linePath`, `areaPath`, `arcs`, `compactNumber`). ## Styling and theming - Colours, type and radii come from CSS custom properties: `--bg`, `--card`, `--text`, `--text2`, `--muted`, `--border`, `--amber` (the accent), `--amber-ink`, `--on-amber`, `--red`, `--green`, `--blue`, `--violet`, `--r-pill`, `--r-card`, `--font-sans`, `--font-mono`. Set one on any element to restyle everything inside it. - Most components expose their own knobs (e.g. `--kbtn-radius`); see the "Customizing" example on each docs page. - Component styles are wrapped in `:where()`, so a plain class selector in app CSS overrides them. Do not use `::ng-deep`, `!important` or copy component CSS; write a normal rule or set a custom property. - `k-drawer` and `k-digits` take `styleClass` to put a class on their inner element. - Overlays (drawer, pop, menu, toast...) take `animation`: a preset name from `KOMETA_ANIMATIONS`, `'none'`, or your own `"in out"` keyframe names, which must be defined in global CSS (component-scoped `@keyframes` get renamed). `[kAnimate]` animates any element on enter or when scrolled into view. ## Design rules the kit assumes - One amber (primary) action per screen: the next step the user should take. Use `severity="secondary"` or `text` for the rest. - The look is dense: 11-13px body text, pill-shaped controls, mono numerals for times and prices. - Prefer a kit component over a native element or a hand-built one (`k-select` over ``. | Name | Binding | Type | Default | Notes | |---|---|---|---|---| | `value` | model (two-way `[( )]`) | `string` | `''` | | | `placeholder` | input | `string` | `''` | | | `ariaLabel` | input | `string` | **required** | | | `clearLabel` | input | `string` | `''` | The "×" button's accessible name; without one the button is hidden from assistive tech (Escape clears natively). | | `size` | input | `"md" \| "lg"` | `'md'` | `md` is a page toolbar (22px); `lg` is the lab's 42px hero. | | `name` | input | `string` | `''` | | | `inputmode` | input | `string` | `''` | | | `maxlength` | input | `number \| null` | `null` | | | `disabled` | input | `boolean` | `false` | | | `readonly` | input | `boolean` | `false` | | | `clearable` | input | `boolean` | `true` | The "×" button once there is text. | | `autofocus` | input | `boolean` | `false` | The page that IS a search (`/search`) opens with the cursor in the question. | ## `k-select` — KometaSelect One choice from a list. The field is a line with the chosen word and a chevron; it opens a glass list in the browser's top layer (so a drawer or a card cannot clip it), flips above when there is no room below and is kept inside the viewport. The chosen row takes the 2px edge. Arrow keys, Home and End move, a letter jumps to the next row that starts with it, Enter or Space picks, Escape closes (and does not reach a drawer behind it), Tab, a click outside, resize and scroll elsewhere close it. `options` are objects read through `optionLabel` and `optionValue` (so a call site moves over as it is). With `group`, each option is a group read through `optionGroupLabel` and `optionGroupChildren`. `value` is matched with `===`; with no match the `placeholder` shows. `prefix` is a muted word before the choice ("Role: Owner"), and `pill` draws the field as a bordered pill for a toolbar instead of a form line. `inputId` lets a `