@assistant-ui/mcp-docs-server 0.2.3 → 0.3.0

package/.docs/raw/docs/(reference)/api-reference/generative-ui/actions.mdx

@@ -1,56 +0,0 @@
----
-title: Generative UI Actions
-description: "Register handlers for model-emitted $action payloads and dispatch them from interactive generative UI components."
----
-
-import { ActionDispatchContext, ActionRegistry, createActionRegistry } from "@/generated/typeDocs";
-
-{/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
-{/* Do not edit manually. */}
-
-{/* api-reference:start */}
-{/* AUTO-GENERATED by scripts/generate-api-reference.mts */}
-{/* Do not edit this block manually. */}
-
-## API Reference
-
-### ActionDispatchContext
-
-Context handed to an [ActionHandler](/docs/api-reference/generative-ui/actions#actionhandler) when an `$action` fires.
-
-<ParametersTable {...ActionDispatchContext} />
-
-### ActionHandler
-
-Resolves a single `$action.type`. Fire-and-forget actions return `void` or a
-promise that resolves to it; human-in-the-loop actions return a value the
-runtime uses to resume the run (see IR doc Open question #2 — the resume
-value is left as `unknown` and documented per-action). The return value is
-handed back to `dispatch`'s caller as `unknown`.
-
-```ts
-type ActionHandler = (
-  ctx: ActionDispatchContext,
-) => unknown | Promise<unknown>;
-```
-
-### ActionRegistry
-
-The host-provided map from `$action.type` to [ActionHandler](/docs/api-reference/generative-ui/actions#actionhandler). This is the single dispatch target for rendered generative UI: every interactive component fires its `$action` here through the injected `$dispatch` (a submit Button defers to its ancestor form's dispatch instead). The payload's `$input` takes one of two shapes: a single value for a standalone control's dispatch (`Select`, `Input`, `DatePicker`, `Checkbox`, `RadioGroup`), or an object keyed by field `name` for a `Form` or a `Card` with `asForm` set. Construct it with [createActionRegistry](/docs/api-reference/generative-ui/actions#createactionregistry) and pass it to `JSONGenerativeUI`.
-
-<ParametersTable {...ActionRegistry} />
-
-### createActionRegistry
-
-<ParametersTable {...createActionRegistry} />
-
-### emptyActionRegistry
-
-A no-op registry used when no handlers are provided. Dispatch resolves to
-`undefined` and logs a warning in dev for unknown types, so a model-emitted
-action with no handler degrades to "does nothing" rather than throwing.
-
-```ts
-const emptyActionRegistry: ActionRegistry;
-```
-{/* api-reference:end */}

package/.docs/raw/docs/(reference)/api-reference/generative-ui/components.mdx

@@ -1,86 +0,0 @@
----
-title: Generative UI Components
-description: Define the component library JSONGenerativeUI can render, including schemas, render functions, and the default vocabulary.
----
-
-import { GenerativeUIComponent, defineGenerativeComponents } from "@/generated/typeDocs";
-
-{/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
-{/* Do not edit manually. */}
-
-{/* api-reference:start */}
-{/* AUTO-GENERATED by scripts/generate-api-reference.mts */}
-{/* Do not edit this block manually. */}
-
-## API Reference
-
-### defaultGenerativeUILibrary
-
-The closed generative-ui vocabulary the factory ships: a fixed set of
-intrinsic components the model may render, each a zod `properties` schema
-plus an unstyled structural `render` (semantic HTML with a `data-aui`
-attribute naming the component, plus `data-aui-<prop>` hooks, for the host
-to style). Users opt in by passing it to
-`new JSONGenerativeUI({ library: defaultGenerativeUILibrary })`, and override
-or extend entries with their own `defineGenerativeComponents`.
-
-```ts
-const defaultGenerativeUILibrary: GenerativeUILibrary;
-```
-
-### defineGenerativeComponents
-
-Authoring helper for a `"use generative"` generative-UI library — the set of
-components the model may render. Each component colocates its `properties`
-schema (kept on every build, drives the tool parameters) with its `render`
-(kept only on the client). Pass the result to [JSONGenerativeUI](/docs/api-reference/generative-ui/json-generative-ui#jsongenerativeui):
-
-```tsx
-"use generative";
-const generative = new JSONGenerativeUI({
-  library: defineGenerativeComponents({
-    Card: {
-      description: "A card.",
-      properties: z.object({ title: z.string() }),
-      render: (props) => <Card {...props} />,
-    },
-  }),
-});
-```
-
-Unlike [defineToolkit](/docs/api-reference/tools/toolkits#definetoolkit), it has **no runtime implementation**. A
-`"use generative"` compiler unwraps the `defineGenerativeComponents(...)` call
-per build, dropping each `render` (and its client-only imports) from the server
-build. Reaching it at runtime means the module wasn't compiled (the directive
-is missing, or it was used outside a `"use generative"` file), so it throws
-rather than shipping client `render` code to the server.
-
-<ParametersTable {...defineGenerativeComponents} />
-
-### GenerativeUIComponent
-
-A component the model is allowed to render, with the schema for its props.
-
-Components opt into prop streaming with `streamProperties`: they render as
-props arrive, so `render` sees `Partial<P>` while `$status` is `"streaming"`
-and the full `P` once it is `"done"`. By default a component opts out and is
-only rendered once its props are complete.
-
-`render` is a function of `props`, not a React component. Direct hook use is
-fine (each node is mounted on its own fiber), but a given node must keep its
-`type` across renders for hook identity to be stable.
-
-<ParametersTable {...GenerativeUIComponent} />
-
-### GenerativeUILibrary
-
-The consumer-provided allowlist of components the model is permitted to
-render. Keys are the `type` values referenced in the generative-ui tree
-(e.g. `"Card"`, `"Button"`); values describe each component.
-
-This registry is the security boundary — any `type` not present is rejected.
-
-```ts
-type GenerativeUILibrary = Record<string, GenerativeUIComponent>;
-```
-{/* api-reference:end */}

package/.docs/raw/docs/(reference)/api-reference/generative-ui/index.mdx

@@ -1,39 +0,0 @@
----
-title: Generative UI API Reference
-description: Spec-driven generative UI for assistant-ui. The data format an assistant streams, the component registry that resolves it, and the renderer that turns it into React elements.
----
-
-{/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
-{/* The page list is generated from exported APIs; edit only the manual prose slot. */}
-
-## Pages
-
-<Cards>
-  <Card title={"JSONGenerativeUI"} href={"/docs/api-reference/generative-ui/json-generative-ui"}>
-    {"Create present and prompt_user tools from a generative UI component library, with options for display mode and action dispatch."}
-  </Card>
-  <Card title={"Generative UI Components"} href={"/docs/api-reference/generative-ui/components"}>
-    {"Define the component library JSONGenerativeUI can render, including schemas, render functions, and the default vocabulary."}
-  </Card>
-  <Card title={"Generative UI Actions"} href={"/docs/api-reference/generative-ui/actions"}>
-    {"Register handlers for model-emitted $action payloads and dispatch them from interactive generative UI components."}
-  </Card>
-  <Card title={"Generative UI Spec"} href={"/docs/api-reference/generative-ui/spec"}>
-    {"The serializable node tree an assistant emits to describe generative UI. Covers the GenerativeUISpec format, its nodes, and the message part that carries the spec."}
-  </Card>
-  <Card title={"Generative UI Rendering"} href={"/docs/api-reference/generative-ui/rendering"}>
-    {"Render generative UI trees, build present-tool schemas, and inspect or serialize model-produced UI nodes."}
-  </Card>
-  <Card title={"Slack Block Kit"} href={"/docs/api-reference/generative-ui/slack"}>
-    {"Convert generative UI trees to Slack Block Kit payloads and decode block_actions interactions back into $action payloads."}
-  </Card>
-  <Card title={"Microsoft Teams"} href={"/docs/api-reference/generative-ui/teams"}>
-    {"Convert generative UI trees to Teams Adaptive Cards and decode Action.Submit payloads back into $action payloads."}
-  </Card>
-  <Card title={"A2UI"} href={"/docs/api-reference/generative-ui/a2ui"}>
-    {"Convert A2UI surface operations into generative UI specs."}
-  </Card>
-  <Card title={"Generative UI Tokens"} href={"/docs/api-reference/generative-ui/tokens"}>
-    {"Shared token arrays used by the default generative UI vocabulary for sizing, color, alignment, and component variants."}
-  </Card>
-</Cards>

package/.docs/raw/docs/(reference)/api-reference/generative-ui/json-generative-ui.mdx

@@ -1,42 +0,0 @@
----
-title: JSONGenerativeUI
-description: "Create present and prompt_user tools from a generative UI component library, with options for display mode and action dispatch."
----
-
-import { JSONGenerativeUI, JSONGenerativeUIOptions, PresentToolOptions } from "@/generated/typeDocs";
-
-{/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
-{/* Do not edit manually. */}
-
-{/* api-reference:start */}
-{/* AUTO-GENERATED by scripts/generate-api-reference.mts */}
-{/* Do not edit this block manually. */}
-
-## API Reference
-
-### JSONGenerativeUI
-
-Client build of [JSONGenerativeUI](/docs/api-reference/generative-ui/json-generative-ui#jsongenerativeui), resolved through the package's
-`default` export condition (browser and SSR).
-
-`present` is a frontend tool that renders the model's `{ $type,...props }`
-tree against the library and resolves immediately. `prompt_user` is a
-human-in-the-loop tool: the model pauses and the rendered UI supplies the
-result. Both draw the tree the same way, so they share one `render`. The
-`actions` registry (if provided) is threaded into the render context so
-interactive components can fire `$action` through `$dispatch`.
-
-<ParametersTable {...JSONGenerativeUI} />
-
-### JSONGenerativeUIOptions
-
-Options for [JSONGenerativeUI](/docs/api-reference/generative-ui/json-generative-ui#jsongenerativeui).
-
-<ParametersTable {...JSONGenerativeUIOptions} />
-
-### PresentToolOptions
-
-Options for [JSONGenerativeUI.present](/docs/api-reference/generative-ui/json-generative-ui#jsongenerativeui).
-
-<ParametersTable {...PresentToolOptions} />
-{/* api-reference:end */}

package/.docs/raw/docs/(reference)/api-reference/generative-ui/rendering.mdx

@@ -1,84 +0,0 @@
----
-title: Generative UI Rendering
-description: Render generative UI trees, build present-tool schemas, and inspect or serialize model-produced UI nodes.
----
-
-import { GenerativeUIRender, GenerativeUIRenderContext, GenerativeUIRenderError, buildPresentParameters, generativeUIToJSX, renderGenerativeUI } from "@/generated/typeDocs";
-
-{/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
-{/* Do not edit manually. */}
-
-{/* api-reference:start */}
-{/* AUTO-GENERATED by scripts/generate-api-reference.mts */}
-{/* Do not edit this block manually. */}
-
-## API Reference
-
-### buildPresentParameters
-
-Builds the JSON schema for the `present` tool from a [GenerativeUILibrary](/docs/api-reference/generative-ui/components#generativeuilibrary).
-
-The model produces a node `{ $type, $key?,...props }` where `$type` selects
-a component, the optional `$key` pins a stable identity for list items that
-may reorder, and the rest are its props. The schema is a flat object: `$type`
-is an enum of the component names, every component's props are merged into
-one optional bag, and `children` recurses via `$defs` so the tree can nest.
-
-It is intentionally flat rather than a per-`$type` discriminated union. Tool /
-function-call schemas (OpenAI and others) require the top-level parameters to
-be a plain object and reject a top-level `oneOf`/`anyOf`/`enum`. So props can't
-be refined per `$type` at the root; the model is guided instead by `$type`'s
-description (which lists each component) and each prop's own description. The
-renderer validates nothing here — an unknown `$type` or stray prop is handled
-at render time — so a looser schema only costs the model a hint, not safety.
-
-<ParametersTable {...buildPresentParameters} />
-
-### GenerativeUIRender
-
-Internal renderer. Resolves a [GenerativeUISpec](/docs/api-reference/generative-ui/spec#generativeuispec) against the consumer
-allowlist. Used by `MessagePrimitive.GenerativeUI` and by
-`MessagePrimitive.Parts` when handling a `generative-ui` part.
-
-<ParametersTable {...GenerativeUIRender} />
-
-### GenerativeUIRenderContext
-
-The render context threaded through [renderGenerativeUI](/docs/api-reference/generative-ui/rendering#rendergenerativeui).
-
-<ParametersTable {...GenerativeUIRenderContext} />
-
-### GenerativeUIRenderError
-
-Thrown when a generative-ui spec references a component name that is not
-present in the consumer-provided allowlist. The allowlist is the security
-boundary in the same-realm rendering path — there is no fallback by
-default. Pass `Fallback` to opt into a soft-fail UX.
-
-<ParametersTable {...GenerativeUIRenderError} />
-
-### generativeUIToJSX
-
-Serializes a generative-UI node to a JSX-like string for display: the "view source" of a model-produced tree. The wire form `{ $type: "Weather", id: "x" }` becomes `<Weather id="x" />`, and nested `children` render between tags: `<Card title="Hi"><Text>hello</Text></Card>`. A model-provided `$key` becomes the JSX `key` attribute.
-
-By default this is a faithful textual rendering, not a parser: text children are emitted verbatim (not HTML/JSX-escaped), so the result is meant to be shown, not re-parsed. Returns `""` for nodes that aren't renderable (no `$type` yet, `null`, booleans).
-
-Pass `{ escape: true }` to make the output safe to paste back into JSX: any string child containing `<`, `>`, `&`, `{`, or `}` is emitted as a JSON-stringified expression (`{JSON.stringify(child)}`) instead of verbatim, while a string child with none of those characters still renders verbatim.
-
-Pass `{ pretty: true }` to pretty-print nested element trees with two-space indentation, while pure text children stay on one line.
-
-<ParametersTable {...generativeUIToJSX} />
-
-### renderGenerativeUI
-
-Renders a generative-ui tree against a [GenerativeUILibrary](/docs/api-reference/generative-ui/components#generativeuilibrary).
-
-The model emits each node as a flat object `{ $type,...props }`. We first
-normalize that wire form into the canonical NormalizedUINode (with
-`children` lifted to a reserved top-level key), then render: each `type` is
-looked up in the library and its `props` are passed to the component's
-`render(props, context)`, with `children` rendered recursively so components
-can nest.
-
-<ParametersTable {...renderGenerativeUI} />
-{/* api-reference:end */}

package/.docs/raw/docs/(reference)/api-reference/generative-ui/slack.mdx

@@ -1,85 +0,0 @@
----
-title: Slack Block Kit
-description: "Convert generative UI trees to Slack Block Kit payloads and decode block_actions interactions back into $action payloads."
----
-
-import { FromSlackBlocksResult, SlackBlocksResult, SlackConversionWarning, ToSlackBlocksOptions, decodeBlockAction, fromSlackBlocks, toSlackBlocks } from "@/generated/typeDocs";
-
-{/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
-{/* Do not edit manually. */}
-
-{/* api-reference:start */}
-{/* AUTO-GENERATED by scripts/generate-api-reference.mts */}
-{/* Do not edit this block manually. */}
-
-## API Reference
-
-### decodeBlockAction
-
-Decodes one structural entry from a Slack `block_actions` payload.
-`$input` is reserved for the runtime selection: a `$input` key inside the
-button's JSON `value` payload is dropped rather than spread into the result.
-
-<ParametersTable {...decodeBlockAction} />
-
-### fromSlackBlocks
-
-Converts Slack Block Kit JSON back into a generative-ui IR tree, inverting
-[toSlackBlocks](/docs/api-reference/generative-ui/slack#toslackblocks). Accepts a blocks array or a `{ blocks }` wrapper;
-malformed input resolves to an empty node list plus a warning, and an
-unrecognized block or action element is skipped with a "dropped" warning.
-Every array read along the way (blocks, fields, options, elements, cards,
-rows, cells) is bounded to its site's cap before it is mapped over, so a
-hostile array (sparse or proxied with a fabricated `length`) is clamped
-with a "clamped" warning instead of stalling the event loop. Never throws.
-
-The Slack shape is lossier than the IR, so some information cannot be
-recovered: a context block's elements always decode as `Caption` (the
-original `Badge` vs `Caption` distinction does not survive the round trip),
-a button's `buttonStyle` is only recovered for the `primary`/`danger` Slack
-styles, a native alert block's `title` and `description` merge into a
-single `description` string, and a card's layout collapses to its `title`,
-a flat `children` list (image, then text, then caption, in that order),
-and `confirm`/`cancel` footer buttons. A section field's label and value
-are split on the first `*`+newline delimiter, so a label or value that
-itself contains that exact delimiter cannot be split back unambiguously.
-A data-table cell that Slack carries as `raw_text` always decodes as a
-string, even when its text is the stringified form of a boolean, since the
-Slack shape does not distinguish a boolean from ordinary text.
-
-<ParametersTable {...fromSlackBlocks} />
-
-### FromSlackBlocksResult
-
-The IR nodes and non-fatal warnings produced by converting Slack Block Kit JSON back into generative UI.
-
-<ParametersTable {...FromSlackBlocksResult} />
-
-### SlackBlocksResult
-
-The blocks and non-fatal warnings produced by Slack conversion.
-
-<ParametersTable {...SlackBlocksResult} />
-
-### SlackConversionWarning
-
-A non-fatal note reported during Slack conversion.
-
-`clamped` removed content to fit a limit, `dropped` discarded a node or one
-of its props and may leave a placeholder note behind, and `fallback` emitted
-the node in a different form than requested.
-
-<ParametersTable {...SlackConversionWarning} />
-
-### toSlackBlocks
-
-Converts a generative-UI tree into Slack Block Kit JSON and downgrade warnings.
-
-<ParametersTable {...toSlackBlocks} />
-
-### ToSlackBlocksOptions
-
-Options that select the target Slack surface.
-
-<ParametersTable {...ToSlackBlocksOptions} />
-{/* api-reference:end */}

package/.docs/raw/docs/(reference)/api-reference/generative-ui/spec.mdx

@@ -1,45 +0,0 @@
----
-title: Generative UI Spec
-description: The serializable node tree an assistant emits to describe generative UI. Covers the GenerativeUISpec format, its nodes, and the message part that carries the spec.
----
-
-import { GenerativeUIMessagePart, GenerativeUINode, GenerativeUISpec } from "@/generated/typeDocs";
-
-{/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
-{/* Do not edit manually. */}
-
-{/* api-reference:start */}
-{/* AUTO-GENERATED by scripts/generate-api-reference.mts */}
-{/* Do not edit this block manually. */}
-
-## API Reference
-
-### GenerativeUIMessagePart
-
-A message part that carries a JSON spec describing UI to render.
-
-Render with `<MessagePrimitive.GenerativeUI components={...} />`. The
-primitive resolves component names against the consumer-provided allowlist
-— any unknown name throws a typed error rather than rendering. Stream-
-friendly: a partially-streamed spec renders progressively.
-
-<ParametersTable {...GenerativeUIMessagePart} />
-
-### GenerativeUINode
-
-A JSON spec describing a tree of UI components to render.
-
-The agent emits a [GenerativeUIMessagePart](/docs/api-reference/generative-ui/spec#generativeuimessagepart) containing this spec, and
-the consumer-provided component allowlist is used to resolve `component`
-names. Any component referenced that is not present in the allowlist is
-rejected with a typed error — the allowlist is the security boundary in the
-default same-realm rendering path.
-
-<ParametersTable {...GenerativeUINode} />
-
-### GenerativeUISpec
-
-The root spec for a generative UI tree.
-
-<ParametersTable {...GenerativeUISpec} />
-{/* api-reference:end */}

package/.docs/raw/docs/(reference)/api-reference/generative-ui/teams.mdx

@@ -1,93 +0,0 @@
----
-title: Microsoft Teams
-description: "Convert generative UI trees to Teams Adaptive Cards and decode Action.Submit payloads back into $action payloads."
----
-
-import { AdaptiveCardResult, TeamsAttachmentsResult, TeamsConversionWarning, decodeSubmitData, toAdaptiveCard, toTeamsAttachments } from "@/generated/typeDocs";
-
-{/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
-{/* Do not edit manually. */}
-
-{/* api-reference:start */}
-{/* AUTO-GENERATED by scripts/generate-api-reference.mts */}
-{/* Do not edit this block manually. */}
-
-## API Reference
-
-### AdaptiveCardResult
-
-The card and non-fatal warnings produced by [toAdaptiveCard](/docs/api-reference/generative-ui/teams#toadaptivecard).
-
-<ParametersTable {...AdaptiveCardResult} />
-
-### decodeSubmitData
-
-Decodes the merged `activity.value` object a Teams bot receives on
-Action.Submit, inverting the `aui` envelope buildSubmitAction nests
-the resume action under. Adaptive Cards fold every other same-card input's
-value into the same submit object keyed by its `id`, so every top-level key
-besides `aui` is collected into `$input` (omitted when there are none).
-`aui` is reserved for the envelope: `toAdaptiveCard` renames any input
-whose id would collide to an unused id derived from it before encoding, so
-a same-card input value can never land on this key. `$input` and `type`
-are reserved on the way out: a `$input` key inside the envelope payload is
-dropped so the slot only ever reflects same-card input values, and the
-envelope's own `type` wins over a payload key of the same name. Every
-collected key (in `payload` or `$input`) is kept as an own data property of
-the returned object, even a `__proto__` or `constructor` key, since the
-object is always built by spreading and `Object.fromEntries` rather than by
-keyed assignment. Envelope keys are read as own properties only, so
-prototype-inherited `aui`, `type`, or `payload` values never dispatch.
-Returns `undefined` for a missing or malformed `aui` envelope; never throws.
-
-<ParametersTable {...decodeSubmitData} />
-
-### TeamsAttachmentsResult
-
-The attachments and non-fatal warnings produced by [toTeamsAttachments](/docs/api-reference/generative-ui/teams#toteamsattachments).
-
-<ParametersTable {...TeamsAttachmentsResult} />
-
-### TeamsConversionWarning
-
-A non-fatal note reported during Teams conversion.
-
-`clamped` removed content to fit a limit, `dropped` discarded a node or one
-of its props and may leave a placeholder note behind, and `fallback`
-emitted the node in a different form than requested. `advisory` changed
-nothing at all and notes content Teams may still render poorly or refuse,
-such as a payload over the byte budget or a `Row` past the recommended
-column count.
-
-<ParametersTable {...TeamsConversionWarning} />
-
-### toAdaptiveCard
-
-Converts a generative-ui tree into a Microsoft Teams Adaptive Card and
-non-fatal conversion warnings. Sizes, weights, and colors map to Adaptive
-Card's semantic enums rather than raw values. An Input/Select/RadioGroup/
-Checkbox/DatePicker whose id would be the reserved RESERVED_INPUT_ID
-is renamed with a warning (see `decodeSubmitData`). Never throws: an
-unknown `$type` is skipped with a "dropped" warning, and a malformed input
-resolves to an empty card plus a "dropped" warning instead of throwing.
-
-<ParametersTable {...toAdaptiveCard} />
-
-### ToAdaptiveCardOptions
-
-Options accepted by [toAdaptiveCard](/docs/api-reference/generative-ui/teams#toadaptivecard) and [toTeamsAttachments](/docs/api-reference/generative-ui/teams#toteamsattachments). Reserved for future extension; no options are currently defined.
-
-```ts
-export interface ToAdaptiveCardOptions {}
-```
-
-### toTeamsAttachments
-
-Converts a generative-ui tree into Teams bot-framework message attachments.
-A root-level `Carousel` becomes one attachment per `Card` child (clamped to
-CAROUSEL_ATTACHMENT_CAP) with `attachmentLayout: "carousel"`;
-anything else converts through [toAdaptiveCard](/docs/api-reference/generative-ui/teams#toadaptivecard)'s engine into a
-single attachment. Never throws.
-
-<ParametersTable {...toTeamsAttachments} />
-{/* api-reference:end */}

package/.docs/raw/docs/(reference)/api-reference/generative-ui/tokens.mdx

@@ -1,62 +0,0 @@
----
-title: Generative UI Tokens
-description: Shared token arrays used by the default generative UI vocabulary for sizing, color, alignment, and component variants.
----
-
-{/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
-{/* Do not edit manually. */}
-
-{/* api-reference:start */}
-{/* AUTO-GENERATED by scripts/generate-api-reference.mts */}
-{/* Do not edit this block manually. */}
-
-## API Reference
-
-### ALERT_TONES
-
-```ts
-const ALERT_TONES: readonly ["info", "success", "warning", "danger"];
-```
-
-### ALIGNS
-
-```ts
-const ALIGNS: readonly ["start", "center", "end"];
-```
-
-### BUTTON_STYLES
-
-```ts
-const BUTTON_STYLES: readonly ["primary", "secondary", "outline", "ghost", "danger"];
-```
-
-### COLORS
-
-```ts
-const COLORS: readonly ["emphasis", "secondary", "alpha-70", "white", "white-70", "white-50"];
-```
-
-### IMAGE_SIZE_TOKENS
-
-```ts
-const IMAGE_SIZE_TOKENS: readonly ["sm", "md", "lg"];
-```
-
-### JUSTIFIES
-
-```ts
-const JUSTIFIES: readonly ["start", "center", "end", "between"];
-```
-
-### TEXT_SIZES
-
-```ts
-const TEXT_SIZES: readonly ["sm", "md", "lg", "xl", "2xl", "3xl"];
-```
-
-### WEIGHTS
-
-```ts
-const WEIGHTS: readonly ["normal", "medium", "semibold", "bold"];
-```
-{/* api-reference:end */}