Purpose
The HASMaster prompt library stores and organizes reusable prompts that power runtime pipelines, assistant behaviors, and controlled authoring workflows.
Canonical Prompt Entry Points
Source Of Truth Rules
- Edit source-controlled prompt files first.
- Do not treat WordPress prompt posts as the authoring source.
- Do not manually edit generated runtime prompt cache files.
Assistant Nudge Workflow
- Source files live under
/mnt/hasmaster_1000/execution_ops/prompts/source/website/assistant-nudges/. - Publish with
python3 /mnt/hasmaster_1000/execution_ops/prompts/tools/publish_assistant_nudges.py. - Validate with
python3 /mnt/hasmaster_1000/execution_ops/prompts/tools/validate_assistant_nudges.py. - The publish step rewrites prompt-library posts, runtime cache artifacts, and execution cache outputs from source.
Manual Journey Prompt Workflow
- Journey prompts live under
/mnt/hasmaster_1000/website/journeys/prompts/. - Stage routing and prompt contracts are governed by
stage-contracts.json. - Publish with
bash /mnt/hasmaster_1000/website/journeys/scripts/publish_journey_prompts.sh.
Prompt Library Standard
- description
- execution context
- system usage
- exactly one canonical code block for the runtime payload
Safety Checklist
- Update source and metadata together when labels, icons, or routing intent change.
- Run publish and validation before testing the site.
- Use Runtime Registries in HASMaster Tools when you need an operator-facing publish/validate surface.