hermes-project-soul

Generates nested SOUL/ knowledge bases and Hermes project-context wiring for repositories.

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/swcstudiospace/aimeecodes --skill hermes-project-soul-swcstudiospace
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hermes-project-soul
Source: https://github.com/swcstudiospace/aimeecodes/tree/main/.aimee/skills/hermes-project-soul
Command: npx skills add https://github.com/swcstudiospace/aimeecodes --skill hermes-project-soul-swcstudiospace

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Large multi-subsystem repositories overwhelm agent context windows, and a single giant context file gets truncated so agents miss critical rules. This Skill builds an on-demand project understanding layer so Hermes and other agents orient quickly without stuffing the entire codebase into one file. ## Core Features & Use Cases - Nested SOUL/ tree generation: Creates a root SOUL.md index plus numbered per-subsystem SOUL.md files covering purpose, key paths, contracts, invariants, and verify commands. - Hermes context wiring: Configures .hermes.md and AGENTS.md correctly, including the critical rule that .hermes.md replaces AGENTS.md auto-injection and must force a tool-read of AGENTS.md. - Invariant capture and maintenance discipline: Extracts hard security and routing rules into both AGENTS.md and a dedicated invariants SOUL file, with a same-change-set update policy. - Use Case: Onboarding agents to a large Rust/Python monorepo—survey the tree, write the SOUL index and subsystem files, wire .hermes.md, and verify each nested file stays small and path-grounded. ## Quick Start Ask the agent to build a SOUL knowledge base for this repository and wire up .hermes.md so Hermes loads AGENTS.md and the SOUL index correctly.

Frequently Asked Questions about hermes-project-soul

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a SOUL knowledge base for a Hermes agent project?▼

Survey the repository tree, read existing AGENTS.md rules, then write a root SOUL/SOUL.md index followed by one small SOUL.md per numbered subsystem folder. Finish by wiring .hermes.md to force-read AGENTS.md and point to the SOUL index.

Why does AGENTS.md stop loading when I add a .hermes.md file?▼

Hermes injects exactly one project context source, and .hermes.md takes priority over AGENTS.md, disabling its auto-injection. The .hermes.md file must explicitly require a tool-read of AGENTS.md on every non-trivial task and summarize hard invariants.

What is the difference between SOUL.md in a repo and ~/.hermes/SOUL.md?▼

The repo-local SOUL/ tree is project knowledge for orientation, while $HERMES_HOME/SOUL.md defines the agent's identity. They are independent files and one is not a substitute for the other.

How large should each nested SOUL.md file be?▼

Keep each nested file around 1-6 KB, focused on orientation with paths and contracts rather than pasted source code. If a file grows past roughly 8-10 KB, split it into further subsystems to avoid context truncation.

When should I not use a repo SOUL knowledge base?▼

Do not use it for Hermes home identity files, one-off README rewrites, or runtime skill packages defined by SKILL.md. It is meant for durable project understanding in multi-subsystem repositories, not single-purpose documentation tasks.