With this approach a script runs once at commit time, reads each source file, and builds a semantic map; feature names pointing to files, exports, and API channels. That map gets committed alongside your code as a single JSON file. When an AI agent needs to find something, it queries one keyword and gets back the exact files and interfaces in under a millisecond.
What you gain: AI agents that navigate your codebase like they wrote it. No context wasted on irrelevant files. No missed connections between a service and its controller. And since the map regenerates automatically on every commit, it never falls out of sync. I added this to my open sourced agentic development platform, feel free to examine it or use it. Any ideas or contributions are always welcome.
selixe_•8m ago
- dynamically generated code - reflection-heavy systems - implicit coupling (shared schemas, conventions, etc)
These are usually where simple maps break down and why people fall back to full-text or embeddings.