What problem does it solve? When changing or debugging lci's symbol navigation features (def, refs, callers, tree, symbols, inspect, browse, find_files), developers need to know which CLI command, MCP handler, or HTTP endpoint implements each behavior, how the reference tracker and symbol store resolve calls, and which tests and golden files pin the expected output. ## Core Features & Use Cases - Surface-to-code mapping: Tables link every CLI verb, MCP tool, and HTTP endpoint to its exact source file and line, from run_def in src/cli/commands.cpp to handle_list_symbols in src/mcp/handlers_explore.cpp. - Core internals documentation: Explains the ReferenceTracker RCU snapshot, receiver-type call resolution, import resolver, PostingsIndex, SymbolStore, and base-63 object ID encoding. - Invariants and traps: Documents that def/refs are text searches decorated with symbol data, that confirmed callers exclude dynamic and unresolved sites, and that /tree risk fields are stubbed zeros. - Use Case: A developer fixing a bug where lci callers misses a typed-receiver call uses this Skill to find resolve_reference_target in reference_tracker.cpp, the pinned resolver tests, and the probe recipes to reproduce the issue. ## Quick Start Use the lci-symbol-navigation skill to find the source code and tests behind the lci callers command and compare its call resolution against an LSP server.
