letrixui

The Letrix UI CLI. It writes components into your project as plain files you own — no runtime dependency on us afterwards, and the CLI itself has zero dependencies, so npx letrixui starts immediately.

npx letrixui login          # authorize this machine (one click in the browser)
npx letrixui init           # tokens, Tailwind preset, components.json
npx letrixui add button     # add components, with their dependencies
npx letrixui list           # everything available, and its tier

Authorization

Paid components need authorization once per machine. login opens letrixui.com with a one-time code already in the link; you click Authorize and the CLI stores an API key for that machine in ~/.config/letrixui/config.json (owner-only permissions). Revoke it from your dashboard and that machine stops working — every other one carries on.

Where no browser can open — CI, Docker, an MCP server — create a named API key in your dashboard and set it in the environment:

LETRIXUI_API_KEY=lxui_… npx letrixui add table

components.json

init writes it, and every later add follows it:

{
  "aliases": {
    "components": "src/components/letrix",
    "recipes": "src/components/letrix/recipes",
    "lib": "src/lib",
    "styles": "src/styles"
  }
}

The imports between the files it writes are computed for your layout, not adjusted afterwards. Without this file, components land in components/letrix/, lib/ and styles/ at the project root.

Scripting

--json makes every command emit exactly one object, success or failure. Exit codes: 0 ok, 1 usage, 3 unknown component, 4 not authorized, 5 file conflict, 6 network.

Full documentation: https://letrixui.com/docs/react/cli