ArtificialSense Labs

Get started with @artificialsenselabs/ui

Zero to a working component in under five minutes — install, load tokens, enable zoneless change detection, and render your first sense- control.

Walkthrough

Six steps

Copy the snippets into a fresh Angular 21 standalone app. The v0.1 public barrel ships eleven exports; more widgets live in the monorepo until they graduate.

  1. Prerequisites

    Angular 21+ standalone application. ArtificialSense UI is built for zoneless change detection, OnPush, and SSR — match that shape for the smoothest integration.

  2. Install packages

    Add the component library and design tokens. Tokens define every `--sense-*` CSS custom property the components expect.

    npm install @artificialsenselabs/ui @artificialsenselabs/tokens
  3. Load design tokens globally

    Import tokens once in your global stylesheet so semantic colours, spacing, and typography are available to every component.

    @use '@artificialsenselabs/tokens' as tokens;
  4. Enable zoneless change detection (recommended)

    Register zoneless CD in `app.config.ts`. Components use signals — no `zone.js`, no `markForCheck()`.

    import { ApplicationConfig, provideZonelessChangeDetection } from '@angular/core';
    
    export const appConfig: ApplicationConfig = {
      providers: [
        provideZonelessChangeDetection(),
        // provideRouter(routes), provideClientHydration(), …
      ],
    };
  5. Import a component

    v0.1 exports eleven primitives (button, input, select, checkbox, alert, badge, spinner, and more). Import standalone components into your own standalone component.

    import { ChangeDetectionStrategy, Component } from '@angular/core';
    import { SenseButtonComponent } from '@artificialsenselabs/ui';
    
    @Component({
      standalone: true,
      imports: [SenseButtonComponent],
      changeDetection: ChangeDetectionStrategy.OnPush,
      template: `<sense-button variant="filled">Save</sense-button>`,
    })
    export class ExampleComponent {}
  6. Run the app and verify

    Start your dev server, confirm the button renders with token-driven styles, and check the browser console for hydration or import errors. If styles look unstyled, tokens are not loaded globally.

    ng serve

Next

Go deeper

Narrative docs, source, and studio services once the first component is on screen.