@kapowaz/design-catalog

Machine-readable catalogs of the @kapowaz design system — components, tokens, and design guidance — for tooling that needs structured access without parsing the live monorepo sources at runtime.

The consumer is @kapowaz/design-mcp; application code shouldn't depend on this package — it's published only so @kapowaz/design-mcp can resolve it as a dependency.

Catalogs

| Resource | Description | | -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | src/resources/component-catalog.json | Every component exported from @kapowaz/components: file path, summary, props, peer-provider requirements, example. Generated from the sources. | | src/resources/token-catalog.json | Every token from @kapowaz/design-tokens: dotted path, CSS variable, getDesignTokens() accessor, and literal value (from tokens.css). | | src/resources/guidance-docs.json | Full body + section table-of-contents for each guidance doc (docs/react/* and the package READMEs). | | src/resources/manual-overrides.json | Hand-curated entries that override or supplement the auto-generated component catalog when a prop shape defeats the lightweight parser. |

Typed imports

import {
  componentCatalog,
  tokenCatalog,
  guidanceDocs,
  type ComponentEntry,
  type TokenEntry,
  type DocEntry,
} from '@kapowaz/design-catalog';

Build artifacts

The three generated catalogs are build artifacts — gitignored, not checked in. manual-overrides.json is the only tracked resource (it's a hand-curated input). Rebuild them via turbo, which also runs first when building the MCP server:

pnpm --filter @kapowaz/design-catalog build
# or, transitively:
pnpm --filter @kapowaz/design-mcp build

turbo.json's @kapowaz/design-catalog#build task declares the cross-package source paths the generators read from, so the catalog is rebuilt whenever a component, token, or guidance doc changes.