Repository navigation
Home
LoreMaster edited this page Oct 10, 2026
·
3 revisions
Start here, then dive into the architecture decisions.
- Getting started — install, connect, and run your first sync.
- Choosing what goes where — send some pages to Pages, some to Confluence and some to the wiki, with exclude and include lists.
- GitHub wiki — publish the Markdown as the repository's wiki pages, beside or instead of a Pages site.
- Generators — pages written from your test reports (and later source docs), synced like any other page.
-
A documentation agent — create an agent for Claude Code, VS Code or
AGENTS.mdthat writes docs the way the sync expects. - Using the MCP server — let an AI agent learn LoreMaster's nesting rules and check its files against them.
- Engine and shells — one Go sidecar over JSON-RPC, thin editor shells, and the alternatives rejected.
- Confluence editions — the verified per-edition API facts the client is built on.
- The MCP server — why it lives in the engine, the six tools, and the "one source of truth" invariant.
- Vertical feature slices — how the Go and TypeScript code is organised.
- Confluence tenant for recorded fixtures — the credentials and setup for recording the #29/#30 fixtures.
See also the project README.md, ROADMAP.md, and
CLAUDE.md at the repository root.
-
LoreMaster documentation
- A documentation agent that follows the LoreMaster structure
- ADR: One Go engine, thin editor shells
- ADR: Vertical feature slices, in Go and TypeScript
- Choosing what goes where
- Command line
- Confluence editions: the facts the design rests on
- Confluence tenant for recorded fixtures
- Generators: pages written from your project's artifacts
- Getting started: syncing a workspace to Confluence
- GitHub Action: the docs site in one step
- Publishing to a GitHub wiki
- The MCP server
- Two-way sync: pull remote edits back, conflict when both sides change
- Using the MCP server
- Watch mode