Prompt Contracts: Treat Prompts Like APIs (Inputs, Outputs, Errors)

The post advocates treating LLM prompts like APIs by defining explicit inputs, output schemas, constraints, and error cases. A one-page contract template is introduced covering purpose, inputs, output schema, constraints, error/fallback handling, and quick tests. A concrete example demonstrates summarizing PR descriptions into structured changelog entries using this contract approach.