/**
 * Design tokens for the `veryfront/ui` primitives.
 *
 * CSS custom properties aligned with the Veryfront Studio design system. When
 * embedded in a host that defines `--background`, `--foreground`, etc., the
 * primitives inherit those tokens; standalone, sensible defaults are injected
 * via `<style>` (see `./tokens.tsx`) on the scope element.
 *
 * This is the base layer both `veryfront/ui` and `veryfront/chat` render
 * against — `chat` re-exports `generateTokenCSS` from here (via its `theme.ts`)
 * so there is a single source of truth for the token vocabulary.
 *
 * NOTE (scope contract): the canonical scope selector is `[data-vf-ui]` — a
 * neutral name for the shared `veryfront/ui` token layer. The historical
 * `[data-vf-chat]` (inherited from when these primitives lived in `chat/ui`) is
 * retained as a **compatibility alias**: every rule below matches BOTH scopes,
 * and every surface that establishes a scope sets both attributes, so existing
 * consumers that target `[data-vf-chat]` in their own CSS / DOM queries keep
 * working. New code should target `[data-vf-ui]`; `[data-vf-chat]` stays
 * supported until a future major removes it.
 *
 * @module react/components/ui/design-tokens
 */
/**
 * The token scope attributes, canonical first. `[data-vf-ui]` is the neutral
 * name new code should use; `[data-vf-chat]` is the retained compat alias.
 */
export declare const UI_SCOPE_ATTRIBUTE = "data-vf-ui";
export declare const UI_SCOPE_ALIAS_ATTRIBUTE = "data-vf-chat";
/** Selector matching either token scope — e.g. for portal `closest()` lookups. */
export declare const UI_SCOPE_SELECTOR: string;
/**
 * Attributes to spread onto a token-scope root element — the canonical
 * `data-vf-ui` plus the `data-vf-chat` compat alias — so every scope establisher
 * shares one source of truth: `<div {...UI_SCOPE_ATTRS} />`.
 */
export declare const UI_SCOPE_ATTRS: {
    "data-vf-ui": string;
    "data-vf-chat": string;
};
/**
 * Generates the scoped CSS for the design tokens. Every rule matches BOTH the
 * canonical `[data-vf-ui]` scope and the `[data-vf-chat]` compat alias, so
 * tokens don't leak to the page and existing consumers keep working.
 *
 * If a host application (e.g. Studio) already defines these CSS custom
 * properties on `:root`, the host values cascade through and our fallbacks are
 * never reached — because we set them on the scope element, which has lower
 * specificity for inherited vars. We intentionally only set them on the scope
 * root so parent-defined tokens take precedence.
 *
 * Dark mode: supports `prefers-color-scheme`, `.dark`, and `[data-theme="dark"]`.
 */
export declare function generateTokenCSS(): string;
//# sourceMappingURL=design-tokens.d.ts.map