Show HN: Pixie-prompts – manage LLM prompt templates like code (opens in new tab)

How existing prompt management solutions work bothers me, it seems to go against programming best practices: the prompt templates are stored in completely separate system from its dependencies, and there’s no interface definitions for using them. It’s like calling a function (the prompt template) that takes ANY arguments and can silently return crap when the arguments don’t align with its internal implementation.

So I made this project according to how I think prompt management should work - strongly typed interface, defined in the code; the prompt templates are co-located in the same codebase as their dependencies; and there’s type-hint and validation for devEx. Doing this also brings additional benefit: because the variables are strong typed at compose time, it’s save to support complex prompt templates with if/else/for control loops with full type safety.

I’d love to know whether this resonate with others, or is it just my pet peeve.