Project Framework
Once your first request works, the next problem is not API syntax. It is where the code and prompt assets should live.
Recommended split
settings/: model settings and environment-specific configprompts/: YAML or JSON prompt assetsservices/: request-side business servicesworkflow/: TriggerFlow orchestration and runtime wiringtools/: tool definitions and MCP registrationtests/: request-level and workflow-level verification
Why this split
- prompts should not be buried inside business logic
- workflow code should stay separate from one-request service code
- tools and MCP integration should remain explicit and reusable
Next
- Request-side prompt assets: Prompt Management Overview
- Workflow boundary: Workflow and Extensions Overview
- Production runtime guidance: Async First