/**
 * MCP prompts — the packaged "consultant" workflows.
 *
 * Tools give an agent ABAP senses; these prompts give it the consultant's
 * playbook for using them, one click from any prompt-capable client (in
 * Claude Code they surface as /mcp__abap-mcp__… slash commands). Same
 * single-source-of-truth discipline as ToolSpec: one PromptSpec object is
 * both the registration and the testable artifact.
 *
 * Prompts steer; they never claim abilities the tools don't have — every
 * instruction grounds in a real tool and repeats the honesty boundaries
 * (static analysis, no system, snapshot-dated released-API data).
 */
import type { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { z } from "zod";
export interface PromptSpec {
    /** Prompt name — shown as the slash-command / prompt id in clients. */
    name: string;
    title: string;
    description: string;
    /** MCP prompt arguments are strings; every one optional and described. */
    args: Record<string, z.ZodOptional<z.ZodString>>;
    /** Build the user-role message text from the (string) arguments. */
    build: (args: Record<string, string | undefined>) => string;
}
export declare const abapReview: PromptSpec;
export declare const abapMentor: PromptSpec;
export declare const abapMigrationPlan: PromptSpec;
export declare const abapFromSpec: PromptSpec;
export declare const ALL_PROMPTS: readonly PromptSpec[];
export declare function registerPrompts(server: McpServer, specs: readonly PromptSpec[]): void;