PQL: Transform sys instructions to XML #24
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🚀 PromptQL Build CompleteBuild Version: Description: PR #24: PQL: Transform sys instructions to XML |
|
No description provided. |
✅ PromptQL Build AppliedBuild Version: |
robertjdominguez
added a commit
that referenced
this pull request
Aug 10, 2025
## Description
> [!NOTE]
> In testing, this reduced response time by 50%!
Converted system instructions from markdown format to structured XML
format for better LLM parsing and execution.
### Changes Made
- **Restructured format**: Converted from markdown headers and bullet
points to XML tags with descriptive attributes
- **Consolidated validation rules**: Moved all CLI and metadata
validation requirements into a single `<validation_protocols>` section
- **Simplified organization**: Grouped related instructions under
logical XML containers (`<technical_requirements>`,
`<output_requirements>`, etc.)
- **Preserved all functionality**: Every instruction and requirement
from the original format is maintained
### Previously...
The system instructions used markdown formatting with headers like `##
Core Principles` and `## Validation Requirements`, making it harder for
the LLM to parse structured requirements.
### Now...
````yaml path=pql/globals/metadata/promptql-config.hml mode=EXCERPT
systemInstructions: |
<system_role>
You are "DocsBot", the AI assistant for PromptQL documentation...
</system_role>
<core_execution_behaviors description="Core instructions...">
- ALWAYS provide a user-facing message before any action block
- Lead with the direct answer - give users what they need immediately
</core_execution_behaviors>
<technical_requirements>
<general_protocols description="These apply to all responses...">
</general_protocols>
<validation_protocols description="Instructions for validating...">
</validation_protocols>
</technical_requirements>
````
The XML structure provides clear semantic boundaries that help the LLM
understand instruction hierarchy and execute validation protocols more
reliably. All original validation requirements, fallback responses, and
technical protocols remain intact but are now organized in a more
machine-readable format.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Note
In testing, this reduced response time by 50%!
Converted system instructions from markdown format to structured XML format for better LLM parsing and execution.
Changes Made
<validation_protocols>section<technical_requirements>,<output_requirements>, etc.)Previously...
The system instructions used markdown formatting with headers like
## Core Principlesand## Validation Requirements, making it harder for the LLM to parse structured requirements.Now...
The XML structure provides clear semantic boundaries that help the LLM understand instruction hierarchy and execute validation protocols more reliably. All original validation requirements, fallback responses, and technical protocols remain intact but are now organized in a more machine-readable format.