import { type SemanticTune } from '@wrongstack/core/design';
import type { Tool } from '@wrongstack/core/types';
type Overrides = Record<string, string>;
export interface DesignInput {
    action?: 'list' | 'use' | 'foundations' | 'set' | 'tune' | 'materialize' | 'verify' | undefined;
    kit?: string | undefined;
    stack?: string | undefined;
    /** action "set" / "use": token overrides, e.g. { primary: "oklch(...)", "dark.bg": "#111" }. */
    set?: Overrides | undefined;
    /** action "tune": high-level knobs, e.g. { radius:"lg", density:"compact", font:"Space Grotesk" }. */
    tune?: SemanticTune | undefined;
    /** action "materialize": output path (project-relative); defaults per stack. */
    out?: string | undefined;
    /** action "materialize": overwrite an existing file. */
    force?: boolean | undefined;
    /** action "verify": explicit files to scan (project-relative). Defaults to a UI-file walk. */
    files?: string | string[] | undefined;
}
export interface DesignOutput {
    action: string;
    kit?: string | undefined;
    stack?: string | undefined;
    output: string;
    /** action "materialize": where the theme file was (or would be) written. */
    path?: string | undefined;
    /** action "verify": adherence score 0..1 and violation count. */
    score?: number | undefined;
    violations?: number | undefined;
}
/**
 * Design Studio tool — progressive disclosure + token enforcement.
 *
 * `list`/`use`/`foundations` browse and pin kits. `set` records structured color
 * overrides (these win over kit tokens). `materialize` writes the active kit's
 * (override-applied) tokens to a real, stack-appropriate theme file so the
 * palette becomes the codebase's source of truth — not just a prompt hint.
 * `verify` scans UI files for off-palette drift.
 */
export declare const designTool: Tool<DesignInput, DesignOutput>;
export {};
//# sourceMappingURL=design.d.ts.map