import type { CclintConfig } from './Config.js';
/**
 * Built-in configuration presets.
 *
 * @remarks
 * A preset is a named, partial {@link CclintConfig} that teams can pull in via
 * `"extends": "@cclint/recommended"` (or an array) instead of hand-writing rule
 * config. Presets are pure data — they carry no discovery, merge, or filesystem
 * concerns. The {@link ConfigLoader} adapter is responsible for resolving an
 * `extends` list into these partials and layering them between the built-in
 * defaults and the user's own config (defaults ← preset(s) ← user).
 *
 * Only named, built-in presets are supported. There is intentionally no
 * file-path or npm-package resolution, so nested/self/cyclic `extends` cannot
 * occur — a preset never itself extends another.
 */
/** Canonical name of the recommended preset. */
export declare const RECOMMENDED_PRESET_NAME = "@cclint/recommended";
/** Canonical name of the strict preset. */
export declare const STRICT_PRESET_NAME = "@cclint/strict";
/** A preset is a reusable, partial configuration layered under user config. */
export type PresetConfig = Partial<CclintConfig>;
/** Registry of built-in presets keyed by their canonical name. */
export declare const PRESETS: Readonly<Record<string, PresetConfig>>;
/**
 * Look up a built-in preset by name.
 *
 * @returns The preset partial, or `undefined` if the name is not a built-in
 * preset (callers decide how to surface the unknown-preset case).
 */
export declare function getPreset(name: string): PresetConfig | undefined;
/** The set of known built-in preset names. */
export declare function getPresetNames(): string[];
//# sourceMappingURL=presets.d.ts.map