What problem does it solve? When working with the lci code index, it is hard to know which .lci.kdl config key, environment variable, or CLI flag actually controls a behavior, where it is parsed in the C++ source, and whether it is even consumed. This Skill answers those questions directly. ## Core Features & Use Cases - Config surface map: Traces every KDL key (index, performance, server, search, insight, synonyms, attributes) to its struct field and production consumer, flagging dead keys. - Layering and precedence: Explains how defaults, user config, project file, CLI flags, and LCI_* env vars overlay each other. - Ignore semantics: Documents gitignore parity, include/exclude glob behavior, hidden-directory skipping, and budget limits. - Use Case: A user asks why their .lci.kdl exclude block stopped ignoring node_modules; the Skill explains that a project exclude block replaces the ~110 default globs rather than extending them. ## Quick Start Ask which config key controls the index file size limit and where it is enforced in the lci source code.
