Reference

Use Reference when you need a fact, not a tutorial: does this symbol exist, what is it called, where does it come from. For how to achieve something use Guides; for the model behind it use Learn.

Prerequisites: none — these pages are a lookup surface; you do not need to have installed anything to check whether a symbol exists.

Public surface

These pages are generated from the same public-surface inventory that enforces documentation ownership, so they list exactly what the packages export — no more, and nothing that has been removed.

Page	Covers
Tokens	token groups, runtime values and types, machine-readable exports from @beemvp/beeui-tokens
Core	public values and types from @beemvp/beeui-core
CLI	every Registry CLI command and flag
Registry	public Registry items that are not component families
Styling	the public CSS entry point

Component families have their own generated pages under Components, and production patterns under Patterns.

Adjacent reference surfaces

Surface	Where
Supported and tested versions	Compatibility
Release channel, version authority and publication state	Migration & versioning
Security reporting and source-ownership implications	Release & security
Performance envelope and budgets	Performance
Machine-readable docs for agents	AI & LLM surfaces
Architecture decisions	Architecture

Publication state

See the release status at the top of this page. Commands on these pages that show pnpm beeui ... or another repository-local form remain available from a checkout as the no-registry-required alternative; they are not the only way to consume the published package.