Atomic Claude

Atomic Claude

 Code graphs, wikis, and research-backed agentic coding. Deterministic tools for nondeterministic workflows, in one opinionated Claude Code config.

 Stop re-explaining your repo to Claude every session.

 Install •
 Concepts •
 Workflow •
 Commands •
 Skills •
 Agents •
 Credits

 atomic serve, the whole tour: wiki docs, search, SQL schema, two agents on the bus, plans, and the code graph.

🌟 Features

🚀 Usage

Everything below is opt-in and composes into one lifecycle. Lost? /atomic-help reads your git state and names one next command; /atomic-help tour walks the whole system.

The workflow

Fresh-context subagents drive the loop as a maker/checker split (Anthropic's evaluator-optimizer pattern): the implementer writes a failing test before any code, the reviewer re-runs tests and gates the diff against the spec, and work commits per green checkpoint. → workflow

Each phase's working state lives in one atomic scratchpad bundle per task — later phases join the same bundle rather than scattering new directories. atomic serve's Plans view lists every bundle and its docs across your worktrees, so you can check what's in flight without cd-ing anywhere. → conventions · serve

Wikis

Wikis are how Claude learns a codebase once instead of every session. Two scopes:

- Repo wiki: docs/wiki/ inside one repository. Build and framework facts, a domain map, cross-cutting notes. Plus one pointer card per domain under .claude/rules/wiki/, injected whenever Claude touches a file in that domain.
- Realm wiki: a Karpathy-style knowledge base you compile with Claude instead of maintaining by hand. A folder holds your repos and the loose material around them; the wiki/ beside them holds per-repo summaries, shared concerns, and knowledge…