poml
Properties
POML (Prompt Orchestration Markup Language)
Overview
Context
Key Principles
- Structured Markup: Uses HTML-like syntax with semantic components
- Separation of Concerns: Content separated from presentation through CSS-like styling
- Modularity: Promotes reusable, component-based prompt design
- Data Integration: Built-in support for diverse data types and external sources
- Developer-Friendly: Familiar syntax and tooling for developers
Mechanism
Examples
Development Toolkit
Misconceptions
- POML replaces plain text prompts → False. POML compiles down to text but provides structure during development
- Only useful for complex prompts → False. Even simple prompts benefit from structure and reusability
- Requires learning a new programming language → False. Uses familiar HTML/CSS-like syntax that developers already know
- Only works with specific LLMs → False. POML is LLM-agnostic and compiles to plain text prompts
Related
- rulesync - Tool that could benefit from POML's templating and include capabilities
- Person/dyoshikawa - Creator of rulesync who discussed POML integration
- Prompt Engineering
- LLM
- Microsoft