promptkit

Everything downstream starts after a prompt is written, and nothing looks at the sentence you're about to send. That sentence is the cheapest artifact in the workflow and the highest-leverage one: a vague instruction doesn't fail loudly, it produces a plausible wrong thing, and the cost lands three steps later in a review pass and a rebuild.

promptkit sharpens the prompt. It never does the work the prompt describes.

Two modes, split by artifact rather than by effort, because their rules genuinely contradict each other:

• task is the instruction you're about to hand an agent in this session. Ephemeral: one send, then it's dead. Context gets baked in, placeholders are forbidden, and it can lean on the repo.
• system is the prompt your application sends on every request. Durable: its variables are the interface, and it has to survive input written by someone trying to break it.

Get the branch wrong and you ship a prompt that fails in exactly the way the other mode guards against. That's why the split exists.

What promptkit is not