Development

These pages document how the Prompt Diary codebase is organized, how the main APIs connect to the product docs, and how to work on the project. They are written for developers modifying the code.

Product-level purposes, principles, and contracts live in the product and generation docs. These development pages explain how the code implements them.

• Architecture — tool shape, codemap, workflow design, CLI interface.
• MCP Tool Architecture — required API and adapter layering for MCP tool implementations.
• Codex Agent Runner — initial needs and basic design for the async Codex SDK wrapper used by generation orchestration.
• Progress Reporting — the events → state → reporter seam that surfaces prepare and generate progress in the terminal.
• Development Guide — environment setup, build, test, lint, release.
• Prompt System — how prompt templates are stored, loaded, and modified.