Distribution & CLI

Two ways to consume

The brain (Navius.Primitives), the behaviour and accessibility you don't want to re-own, is a versioned package reference. A styled layer is the opposite: it's copied into your project as source, so every class is yours to edit.

The navius CLI

List what's available, then add a component. The CLI copies its source (plus anything it depends on) into your project and rewrites the namespace to match yours. The installed tool uses its bundled zits/ui registry by default; local development can still point at a repo checkout with --root or --registry.

# install the preview tool
dotnet tool install -g navius --prerelease

# see everything available
navius list

# copy a component (and its dependencies) into your project
navius add dialog --to ./src/MyApp --namespace MyApp.Ui

The registry

The registry is plain JSON modelled on the registry-item schema, so anyone can host their own. Each item lists its files and its registryDependencies, which the CLI resolves transitively (e.g. dialog pulls in core).

Code you own

After navius add, the styled component is a file in your repo: no wrapper package, no theme override layer. Edit a class and you're editing your own source, while the brain underneath keeps the behaviour correct. For a complete, ready-made styled layer see zits/ui.