PromptOT

A system prompt shouldn't be a string buried in your codebase. Most teams start there anyway - a PM softens the tone, an engineer adds a variable, a reviewer adds a guardrail, all in the same file. Then something breaks in production, and there's no diff worth reading, no way to see what changed, and no way back except a full deploy.

Teams don't need another place to store prompts - they need the same tooling their code already has. Most tools give you a text box and nothing else.

We started by mapping how teams actually work with a prompt - not as one block of text, but as five distinct concerns getting edited by different people for different reasons. Every part of PromptOT, from the block editor to the delivery API, was designed backward from that split.

That principle carried through every layer, not just the editor. A tone change becomes a role edit, not a full rewrite. A safety rule becomes its own guardrail, not a line buried near the output format.