import type { RepoStack } from "../profile/scan.js";
/**
 * Canonical context-dir content. Everything routes through {@link lines} /
 * {@link frontmatter} so golden-file tests stay byte-stable (no dates, no
 * random ordering, single trailing newline). `dir` is the context directory
 * name (`ctx.contextDir`) so every generated path/reference honors the override.
 */
/**
 * Dense routing index — the single entry point an agent loads first. Lists what
 * each context file holds and *when* to load it (progressive disclosure), so a
 * model pulls `architecture.md` only for design work, `conventions.md` only when
 * writing code, etc. Kept ~30 lines on purpose.
 */
export declare function indexDoc(dir: string): string;
/**
 * Architecture context — the "Detected stack" / "Overview" / "Entry points"
 * blocks are auto-populated from the profiler so the file is useful immediately;
 * the prose sections remain author-fill prompts.
 */
export declare function architectureDoc(dir: string, stack: RepoStack): string;
/**
 * Conventions context — coding-style / testing lines are seeded from the detected
 * language, linter, and test command; naming/commit sections stay author-fill.
 */
export declare function conventionsDoc(dir: string, stack: RepoStack): string;
/**
 * The agent-executable completion playbook. The harness lays down skeletons; this
 * tells an AI agent exactly how to FILL them from the code — so the harness
 * self-completes instead of waiting on a human. Stack-aware (entry points,
 * commands, frameworks come from the profiler) and evidence-first.
 */
export declare function setupTasksDoc(dir: string, stack: RepoStack): string;
/**
 * The post-setup validation playbook. An AI agent runs these checks against the
 * REAL system and gives the user a final verdict — explicitly separating what the
 * agent confirmed from gaps only a human can unblock, with workarounds. Conditional
 * sections key off files actually present (`.kiro/`, `.devcontainer/`, the workspace
 * marker), so one checklist fits every setup.
 */
export declare function validationDoc(dir: string, stack: RepoStack): string;
/**
 * A write-once project-guardrails seed. aih fills the detected facts AND derives
 * framework/stack-specific guardrails; the agent fleshes out the rest per
 * `SETUP-TASKS.md`. Write-once so the agent's work is never overwritten on a re-run.
 */
export declare function projectGuardrailsDoc(dir: string, stack: RepoStack): string;
/** Tasks skeleton — section headers an author fills in per repo. */
export declare function tasksDoc(dir: string): string;
/**
 * The INDEX/SKILL pattern in miniature: YAML frontmatter ({@link frontmatter})
 * giving the skill a `name` + `description` (the trigger), then a few numbered
 * steps. Real skills replace this; its job is to show the shape.
 */
export declare function exampleSkillDoc(): string;