Skip to content
Bitsy UI 0.x
Theme
Menu: Introduction
  1. Docs
  2. Get started

Introduction

Bitsy UI Core gives projects a restrained starting point: semantic tokens, reset and base styles, a disciplined light and dark baseline, the first two Bits, and a deliberately small utility layer.

The shortest credible path

The docs should make adoption obvious before they ask you to inspect architecture details.

  1. Install @bitsyui/core and import it once.
  2. Optionally generate a starter override file with @bitsyui/cli.
  3. Use the docs controls to verify that appearance and typography can shift without changing structure.
pnpm add @bitsyui/core
pnpm dlx @bitsyui/cli init bitsy.css --dry-run

/* app.css */
@import "@bitsyui/core";

What exists today

Bitsy is still intentionally small. These are the few surfaces that need to stay clear and well-related.

Foundation

@bitsyui/core

One import path for tokens, theme, reset, base defaults, and the first Bit styles.

Bits

packages/bits

Button and Text Field keep their implementation, Bit definition, and Bitsy Guide together.

CLI

@bitsyui/cli

A narrow setup companion that generates a starter stylesheet instead of scaffolding an app.

Validation

Docs and Storybook

Docs explain adoption and customization. Storybook remains the validation surface.

How to read the docs

Stay on the shortest route for the job you are actually doing.

For adopters

Start with Setup, then review Tokens, Themes, and Typography.

Use Button and Text Field when you want to see the first explicit Bit contracts.

For contributors

Use Architecture for the workspace split, then continue into README.md, AGENTS.md, and internal/ when the work touches architecture or operating rules.

Bitsy UI is MIT licensed. Source on GitHub.