Brf.it's interface-first angle resonates. We built a little service-map pipeline that uses tree-sitter to dump exported functions, public types, and a lightweight dependency graph before hitting the model. Instead of XML I emit one line per symbol (`module::symbol | signature | return | doc`) so the agent sees the shape of the repo without the implementation noise and the dependency graph gives it enough flow context to answer architecture questions. When I combine that dump with the docstrings and a list of entry points, Claude (or any agent) routes to the right files in one shot. Do you plan to bake the graph metadata into the interface output or keep it as a separate layer?