/**
 * Decision returned by `decideNoFrameworkHit` for the
 * "non-empty dir, no supported framework detected" branch of the
 * existing-project gate. Kept as a pure helper so it can be unit-
 * tested without driving the CLI through a child process.
 *
 *   - `scaffold-subdir`: fall through to `runCreateFlow`, which will
 *     prompt for a project name and scaffold into `<dir>/<name>`.
 *   - `fatal`: refuse to proceed; the caller should surface the
 *     usual "not empty / not a known framework" error.
 */
export type NoFrameworkHitDecision = 'scaffold-subdir' | 'fatal';
/**
 * Decide what to do when the target directory has files but doesn't
 * look like any supported framework. Interactive runs fall through to
 * the normal create flow (which will scaffold into a new subdirectory
 * via the project-name prompt); non-interactive runs hard-fail because
 * there's no way to ask the user for a subdir name.
 */
export declare function decideNoFrameworkHit(opts: {
    isInteractive: boolean;
}): NoFrameworkHitDecision;
/**
 * True when `dir` contains no user-visible content. Dotfiles in
 * `SCAFFOLD_EMPTY_IGNORED` (e.g. `.git`) do not count; anything else
 * does. Missing directory counts as empty.
 */
export declare function isDirEmptyForScaffold(dir: string): boolean;
export declare const createProjectSubcommand: import("../../types.ts").SubcommandDefinition;
//# sourceMappingURL=create.d.ts.map