Prompts (catalogue)

type: module path: "@root/src/PuduLangMcp/Domain/Catalog/Prompts.pudu" fidelity: Active domain: "[[domain/Prompt]]" grammar: "[[grammar/pudu]]" depth_score: 0.4 depth_status: MODERATE coupling: 1 interface_stability: 0.75 tags: [module] aliases: [Prompt Catalogue]

Purpose

The prompt templates this server offers and their rendering into messages.

Interface

Signatures

export type PromptArgument = { name: Str, description: Str, required: Bool }
export type PromptSpec = { name: Str, title: Str, description: Str, arguments: Array[PromptArgument] }

export const CONVENTIONS: Str
export fn all() -> Array[PromptSpec]
export fn toJson(spec: &PromptSpec) -> Json.Json
export fn render(name: Str, arguments: &Json.Json) -> Result[(Str, Str), RpcError.ProtocolError]   // (description, user text)

Linkage

• Requires: [[src/PuduLangMcp/Errors/RpcError]], [[src/PuduLangMcp/Utils/JsonAccess]].
• Consumed by: [[src/PuduLangMcp/App/Prompts]].

Algorithm

render finds the spec (unknown name: InvalidParams), requires every required argument as a non-blank string (InvalidParams naming it), and substitutes the arguments into the template. Every template ends with CONVENTIONS: the language rules from [[grammar/pudu]]'s prohibited patterns and the verification workflow (check, format, lint, test).

Negative Logic (Prohibited Paths)

• Arguments are inserted as given, inside fenced blocks where they are code; never evaluated.

Edge Cases

• A non-string argument value is InvalidParams; prompt arguments are strings by definition.

Depth

DEPTH 0.4.

Grill Log

• Q: Should prompts embed documentation text? A: No; they name the tools that fetch it, so the model reads current text instead of a copy in the prompt.

Referenced by

[[src/PuduLangMcp/Domain/Catalog/_MOC]]