Registry

@tailng-ui/registry defines the canonical ownable surface: installable names, generated files, and import metadata for each supported item.

What the registry stores

• canonical component names
• aliases resolved by the CLI
• generated file paths and file contents
• explicit install metadata such as import symbols and import path

Lookup helpers

import { getRegistryItem, listRegistryItemNames } from '@tailng-ui/registry';

const names = listRegistryItemNames();
const button = getRegistryItem('button');

Install metadata

The registry now carries explicit install metadata, so docs and CLI no longer infer import symbols from source files. That keeps generated snippets stable and testable.

Contract with docs and CLI

The docs ownable pages, README surface, and CLI all read from the same registry contract. That is the main safeguard against drift.