Reference

The public exports and runtime surfaces you should depend on when building with @clily/core.

clily intentionally keeps the root package API narrow.

That is a good thing.

It means most downstream code should depend on a small set of stable exports instead of internal schema plumbing or help-generation internals.

Runtime injection patterns

Compare the Deno-style and captured-runtime examples to understand how clily decouples command logic from process globals.

Public API

The root-level exports intended for downstream consumers of @clily/core.