Hermes BibleUnofficial Docs
← All docs Docs / Developer Guide

Prompt Assembly

Hermes deliberately separates: cached system prompt state ephemeral API call time additions This is one of the most important design choices in the project beca

Developer Guide
Section
Developer Guide
Source
hermesbible.com/docs/developer-guide/prompt-assembly

Hermes deliberately separates: cached system prompt state ephemeral API call time additions This is one of the most important design choices in the project beca

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. Cached system prompt layers
  2. Concrete example: assembled system prompt
  3. Persistent Memory
  4. User Profile
  5. Skills (mandatory)
  6. AGENTS.md
  7. How SOUL.md appears in the prompt
  8. How context files are injected
  9. Context file discovery details
  10. API-call-time-only layers
  11. Memory snapshots
  12. Context files
  13. Skills index
  14. Supported prompt customization surfaces

Section map

Cached system prompt layers

Maps cached system prompt layers to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Concrete example: assembled system prompt

Maps concrete example: assembled system prompt to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Persistent Memory

Maps persistent memory to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

User Profile

Maps user profile to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Skills (mandatory)

Maps skills (mandatory) to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

AGENTS.md

Maps agents.md to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

How SOUL.md appears in the prompt

Maps how soul.md appears in the prompt to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

How context files are injected

Maps how context files are injected to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Developer Guide doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: Cached system prompt layers, Concrete example: assembled system prompt, Persistent Memory, User Profile, Skills (mandatory). Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: prompt, assembly, deliberately, separates, cached. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitDeveloper Guide documentation

Use when you need orientation for prompt assembly before applying exact upstream commands.

Verify firstCached system prompt layers

Open the source anchor for Cached system prompt layers and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Developer Guide, then open the linked source page for exact current syntax.
  2. Start with the source section for Cached system prompt layers; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for Concrete example: assembled system prompt if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

External messages

Keep human review before sending public posts, customer messages, trading instructions, or team notifications.

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page