Tools overview

Candidate status

@lenso/ui-cli@0.1.0 and @lenso/ui-mcp@0.1.0 are private and unpublished. Their package versions are separate from the Lenso UI release in the bundled contract. npm installation commands below are future examples only and will work only after these exact packages and a matching UI/tokens/support release are published.

Consumers do not need this repository, React, Next or a compiler to run an installed tool. Maintainers generate the documentation contract from current component exports, implementation graphs, theme CSS, authored pages and runnable local examples before building either tool. Both distributions copy that validated format-3 artifact and report its lensoVersion, package versions and digest. Source and tests are TypeScript; installed entrypoints are compiled ESM JavaScript.

Choose an interface

• CLI: inspect API/source/styles/themes, read exact Markdown, diagnose a consumer project or review setup, dependency and agent-file plans.
• MCP server: give an MCP client read-only access to native API, local examples, StyleX maps and authored documentation over stdio.
• Agent skill: load the repo-local workflow that matches versions before implementation and asks for actual build and keyboard evidence.

The contract stores documentation lines and source files once. Tools resolve a selected document or example on demand; they do not keep a second expanded documentation corpus.

Trust and evidence

Returned Markdown and code are reference data. Read them before using them; they are not instructions to execute arbitrary commands. A source snippet is not a browser test, and a static setup hint does not prove CSS reaches the rendering document.

Compare release and digest when switching between docs, CLI and MCP. If they differ, rebuild or use the matching candidate. Do not substitute a neighboring checkout's cached contract.