@bitsyui/core
One import path for tokens, theme, reset, base defaults, and the first Bit styles.
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 docs should make adoption obvious before they ask you to inspect architecture details.
@bitsyui/core and import it once.@bitsyui/cli.pnpm add @bitsyui/core
pnpm dlx @bitsyui/cli init bitsy.css --dry-run
/* app.css */
@import "@bitsyui/core"; Bitsy is still intentionally small. These are the few surfaces that need to stay clear and well-related.
@bitsyui/coreOne import path for tokens, theme, reset, base defaults, and the first Bit styles.
packages/bitsButton and Text Field keep their implementation, Bit definition, and Bitsy Guide together.
@bitsyui/cliA narrow setup companion that generates a starter stylesheet instead of scaffolding an app.
Docs explain adoption and customization. Storybook remains the validation surface.
Stay on the shortest route for the job you are actually doing.
Start with Setup, then review Tokens, Themes, and Typography.
Use Button and Text Field when you want to see the first explicit Bit contracts.
Use Architecture for the workspace split, then continue into README.md, AGENTS.md, and internal/ when the work touches architecture or operating rules.