Documentation

How to create your soul.md and install the Manoma MCP server.

Templates

Start from a pre-filled example based on your role.

founder.md— Founder/CTO, product + eng
engineer.md— Software engineer
designer.md— Product/UX designer
pm.md— Product manager

Quick start

Add the MCP server to Claude Desktop, Cursor, or any MCP-aware client:

{
  "mcpServers": {
    "manoma": {
      "command": "npx",
      "args": ["-y", "manoma-mcp"]
    }
  }
}

Restart the client and send a message. On first run, manoma auto-creates a starter ~/soul.md and the AI welcomes you with what just happened.
Open ~/soul.md and fill in the placeholders — start with /identity and /values. Or copy a template over the top. Or just ask the AI: “help me fill in my soul.md.”

Want soul.md somewhere else? Set SOUL_MD_PATH in the MCP config env block. Common patterns: a private git repo (history + sync) or a cloud-synced folder (iCloud, Dropbox). Never a public repo — soul.md is personal.

How injection works

soul.md can be long — hundreds of lines of identity, skills, and memory. Stuffing it all into every prompt would waste tokens and bury the signal. Instead, manoma assembles a focused injection per message, under a 2,500-token budget.

Three tiers decide what gets in:

Always — who you are: Identity, values, voice, writing style, skills summary. Loads every time, no matter what you're asking.
By mode — what you're doing: Your current focus and mode-specific sections. Work mode pulls in /now and recent decisions; creative mode leans on preferences and intuition. Switch modes, switch context.
On trigger — what the message is about: Deep-dive sections (specific skill domains, past decisions, lessons, people) only load when keywords in your message match the section's triggers. Ask about pricing → pricing skills and decisions load. Ask about code → they don't.

When the budget tightens, low-priority sections truncate first. Your core identity always makes it through — even if a deep-dive gets trimmed.