import { type StoreFs } from './store/index.js';
export { PRESET_DIR, PRESET_STEMS, presetFilePath, presetContext } from './preset-registry.js';
/**
 * The materialized presets by file stem, derived from the catalog — the registry names the
 * stems, the catalog owns the templates, and this join is the only place the two meet. It
 * used to be a second hand-maintained table re-binding the same generated constants, so a
 * seventh quality preset was two edits with nothing checking they agreed; now a stem with no
 * catalog row simply vanishes from this map, which `presets.test.ts`'s exact key-set
 * assertion turns into a failure.
 */
export declare const PRESETS: Readonly<Record<string, string>>;
/**
 * Materialize every preset into `<cwd>/.the-framework/presets/<name>.md` so an on-before-mergeable
 * TODO entry's `filePath` resolves to a real file the agent can open (#326). The files keep
 * the `${{ tf.params.what }}` blank unrendered: the entry tells the agent what to set it to.
 * The package ships the presets compiled (`files: ["dist"]`), so they land on disk only once
 * written here. Overwrites, so a re-install refreshes them to the installed framework version.
 */
export declare function materializePresets(cwd: string, fs?: StoreFs): Promise<void>;
//# sourceMappingURL=presets.d.ts.map