Thriving Thriving TypeScript TS JavaScript JS
↑ 34 ?
ontology-atlas wlsdks/ontology-atlas

Understand what your codebase builds, why it is structured that way, and what a change could affect. One shared Markdown ontology for humans and coding agents—visualized for people, accessible to agents through MCP, and reviewed with Git. Local-first. Open source.

https://ontologyatlas.com/en/download/ ↗
HEALTH ? 90 / Healthy
// solo builder// release machine knowledge-graphontologyai-agents-frameworkcode-visualizationcodebasecoding-agentsdeveloper-toolsimpact-analysismcp-serverontology-engineering ?

// readme

English | 한국어 | 日本語 | 简体中文

A map of what your code does and why, kept as Markdown in your repository
and read by both you and your coding agent.

Why

Coding agents now change code faster than a team can keep a picture of it in their heads. Atlas keeps that picture beside the code: what each part is for, which files implement it, what depends on what, and what nobody knows yet. Your agent reads it before a task and proposes updates after; you keep, correct or reject each change as a Markdown diff.

  • Your agent starts with context. Claude Code, Codex, Cursor and Antigravity read the concepts, code paths, dependencies and open questions a task touches, over MCP.
  • You own the record. One Markdown file per concept in an atlas/ folder, versioned and reviewed in Git like the code.
  • You decide what is true. Agent proposals stay proposals until you accept them.
  • It says what it does not know.…