Practical Notes
- Quant: keep prompts in git and require PR review for
.promptychanges. - Data point:
.promptyfiles embed model/provider settings next to the template.
Pattern: prompt as an interface contract
Use .prompty as a contract between product and engineering:
- define inputs (variables),
- define provider + model settings,
- and keep the prompt body readable Markdown.
Pattern: run the same prompt in three places
- In VS Code for authoring and preview.
- In Python for batch jobs / eval harnesses.
- In TypeScript for web backends.
This reduces "works on my machine" drift where the template differs per runtime.
FAQ
Q: Is Prompty stable? A: It’s labeled v2 alpha in the repo; expect API/file-format changes.
Q: Can I use it without VS Code?
A: Yes. You can invoke .prompty from Python or TypeScript runtimes.
Q: How do I keep secrets out of git?
A: Reference env vars in connections (e.g. ${env:OPENAI_API_KEY}) instead of hardcoding.