Why Use Prompt Registry?
- Iterate faster - Update prompts without code changes
- Version control - Track prompt history and rollback
- A/B testing - Test different prompts in production
- Collaboration - Non-engineers can edit prompts
Creating a Prompt
- Go to Prompt Registry in your project
- Click New Prompt
- Enter a name (e.g.,
summarization-system-prompt) - Write your prompt content
- Click Save
Prompt Structure
Each prompt has:- Name - Unique identifier (slug format)
- Content - The prompt text
- Variables - Placeholders like
{{user_name}} - Version - Auto-incremented on each save
- Tags - For organization
Using Variables
Include variables in your prompts:Fetching Prompts
Python
TypeScript
Versioning
Every save creates a new version:| Version | Date | Author | Note |
|---|---|---|---|
| v3 | Today | Alice | Added tone guidance |
| v2 | Yesterday | Bob | Fixed typo |
| v1 | Last week | Alice | Initial version |
Rollback
To rollback to a previous version:- Click the version in history
- Click Restore
- This creates a new version with the old content
Environments
Use different prompts per environment:Caching
Prompts are cached locally to minimize latency:- Default TTL: 60 seconds
- Force refresh:
muxx.get_prompt("name", cache=False)
Best Practices
Use descriptive names
Use descriptive names
customer-support-system-v2 is better than prompt1.Document with tags
Document with tags
Test before promoting
Test before promoting
Test new versions in staging before production.
Keep prompts focused
Keep prompts focused
One prompt per purpose. Don’t combine unrelated instructions.