Packages

Overview

Hex UI ships as 8 npm packages. The split keeps release cadences independent: a token-value tweak doesn't force every consumer to retest the components surface, and shipping a new MCP tool doesn't gate the design-token work.

Most apps install @hex-core/components + @hex-core/tokens as runtime dependencies, then invoke the CLI and MCP server via pnpm dlx / npx. The other four runtime packages (themes, registry, payload, preview) are pulled in only when needed.

Runtime packages

These packages travel inside your node_modules. Pin them in package.json.

pnpm add @hex-core/components \
  @hex-core/tokens \
  @hex-core/themes \
  @hex-core/registry \
  @hex-core/payload

• @hex-core/components v1.4.0

  59 Radix + CVA components incl. layout primitives + ColorPicker, Tailwind v4 entry.

• @hex-core/tokens v1.2.2

  HSL design tokens, theme presets, and CSS/Tailwind transformers.

• @hex-core/themes v0.1.1

  Premium theme catalog — midnight, ember, and future presets.

• @hex-core/registry v0.3.1

  Zod schemas + TypeScript types for components, themes, and recipes.

• @hex-core/payload v0.2.1

  Pure-function builders for the canonical LLM context markdown.

Tools

These packages are invoked, not depended on. Run them via pnpm dlx, npx, or your MCP client's command field.

• @hex-core/cli v0.2.3

  The hex binary — init, add, list, theme set, recipe add.

• @hex-core/mcp v0.4.2

  Stdio MCP server: emit_app_context, emit_figma_tokens, resolve_spec, and more.

• @hex-core/preview v0.2.0

  DemoSurface wrapper for showcasing components on flat-white pages.

For LLMs

Two text/plain surfaces summarize the whole stack for AI agents and crawlers:

• /llms.txt — short index of every package + key URLs.
• /llms-full.txt — concatenated mini-guide bundle. One fetch ingests the whole stack.
• /studio/copy — canonical paste-into-LLM markdown for any theme + component selection, including a live ## Packages section.