The bottleneck for AI coding assistants isn't intelligence — it's navigation

You ask Claude about a function. It gives you a confident, detailed explanation. You build on it for an hour. Then you find out it was wrong. Or: you change a function, tests pass, you ship. Three days later — four other places called that function, all broken. Claude never mentioned them. Same root cause: Claude doesn't have a way to navigate your codebase. The core idea Turn your entire repo into a graph. Use BFS + LSP to search and traverse it. /generate-index → build the graph (deterministic script + AI refine) ↓ AI_INDEX.md → the graph itself (adjacency list — nodes are domains, edges are connections) ↓ /investigate-module → read a specific node (grounded, with sources) /trace-impact → BFS along the edges (find everything a change affects) Drop a bug or a feature request anywhere on this graph, and the system traces every connected path to find what's affected — before you write a single line of code. What makes this AI_INDEX different There are dozens of AI_INDEX templates. Most