All project context — architecture, patterns, build commands, conventions, debugging notes, and roadmap — lives on the demarkus-soul MCP server.
mark_fetch/index.md— get the hub pagemark_fetch/patterns.md— build commands, code style, workflowmark_fetch/guidelines.md— hard rules for code quality, must read before writing code- Fetch other pages as needed:
/architecture.md,/debugging.md,/roadmap.md - If MCP is unavailable, stop and ask the user before proceeding
- Update soul pages when learning something new
- Use natural language; avoid overusing "-" within sentences. For bullet points, "-" is still preferred.
- Use
mark_appendfor journal entries and incremental notes - Always use
expected_versionfrom a prior fetch when publishing or appending
- Add a journal entry to
/journal.mdif something significant happened
/index.md — Hub page, links to all sections
/architecture.md — System design, module boundaries, key decisions
/patterns.md — Code patterns, build commands, conventions, workflow
/guidelines.md — Hard rules for code quality, must read before writing code
/debugging.md — Lessons from bugs and investigations
/roadmap.md — What's done, what's next
/journal.md — Session notes and evolution log
/thoughts.md — Agent reflections and ideas
/guide.md — Setup instructions for demarkus-soul
- Agents should never store the plans in their own vendor specific folder
- The agent should always publish the plan to demarkus soul instead