Hermes Agent Set Up Files

Hermes loads its global files from ~/.hermes/ and project instructions from the repository root, checking .hermes.md → HERMES.md → AGENTS.md → CLAUDE.md and using the first match.

Core Agent Identity

SOUL.md

The agent's global identity, personality, tone, and communication style — loaded separately from project instructions.

~/.hermes/SOUL.md

USER.md

The user's preferences, communication style, and profile. Loaded at session start.

~/.hermes/memories/USER.md

IDENTITY.md

Optional

The agent's name, presentation, and self-description, kept apart from behavioral instructions.

~/.hermes/IDENTITY.md

AGENTS.md

Project-specific instructions. Nested AGENTS.md files can be discovered as Hermes enters subdirectories.

<project-root>/AGENTS.md

Hermes Configuration & Instructions

.hermes.md

Project-specific instructions. First in the priority order Hermes checks.

<project-root>/.hermes.md

HERMES.md

Project-specific instructions, used when no .hermes.md is present.

<project-root>/HERMES.md

CLAUDE.md

Project-specific instructions, used as the last fallback in the priority order.

<project-root>/CLAUDE.md

INSTRUCTIONS.md

Optional

Standalone operating instructions referenced from the main instruction file when it grows too large.

<project-root>/INSTRUCTIONS.md

RULES.md

Optional

Hard rules and constraints the agent must follow, kept short and unambiguous.

<project-root>/RULES.md

Memory System

MEMORY.md

Durable environment facts, project conventions, lessons, and other agent memory. Loaded at session start.

~/.hermes/memories/MEMORY.md

Skills & Capabilities

SKILL.md

The entry file for each reusable Hermes skill. A skill may reference additional Markdown documents under folders such as references/ or examples/.

~/.hermes/skills/<skill>/SKILL.md

Hermes also recognizes .cursorrules and .cursor/rules/*.mdc, although those do not use the .md extension.