CreatmanCEO/ai-context-hierarchy
OtherLive in production🇬🇧 English · 🇷🇺 Русский
Three-level context hierarchy for AI coding agents — featured in Graphify v5.0 roadmap. Stop re-explaining your codebase every session. Works with Claude Code, Cursor, Codex, Gemini CLI, Claude Desktop.
- Python100.0%
1 Review
This is a thoughtful, useful pattern repo rather than a heavy framework, and that positioning works well. The README does a strong job explaining the actual pain point: agents repeatedly rediscovering the same project structure, deployment details, and file locations instead of starting from a maintained context map. I especially liked that the project does not stop at an essay. It includes Level 0 and Level 1 templates, platform-specific guides for Claude Code, Claude Desktop, Cursor, Codex, and Gemini CLI, a real multi-project example, and small Python parsers for Claude Code JSONL and Claude Desktop exports. That makes the idea immediately testable instead of just conceptual.
The repo also shows good maintenance instincts for a young project. It has an MIT license, a contributor guide with clear priorities, a changelog, bilingual README coverage, and a GitHub Actions workflow that validates internal Markdown links, required files, template sections, and Python syntax. The latest Validate workflow run on April 30, 2026 passed. The Graphify issue link gives the project some credible external validation, and the README’s limitations section is refreshingly honest about the pattern being a convention, not a safety mechanism or automatic memory system.
The main thing I would improve is verification depth. The parser scripts are useful, but the CI currently only compiles them; a couple of fixture-based tests for Claude Code JSONL and Claude Desktop exports would make contributors less likely to break the YAML/frontmatter contract. I would also consider adding one short “before/after” recorded example with exact inputs and generated files, because the benchmark table is persuasive but would be stronger if readers could reproduce at least one case locally. Since there are no releases yet, tagging 0.2.0 would also make the changelog feel more concrete. Overall, this is a well-scoped developer-tooling repo with unusually good documentation and a clear audience: people using multiple AI coding agents across multiple projects who want less repeated reconnaissance and more durable project context.
