What problem does it solve? Working on lci's search engine requires knowing which of the four surfaces (CLI search, CLI grep, MCP search tool, HTTP POST /search) owns a behavior, where ranking and trigram narrowing live in the C++ tree, and which goldens and differential tests pin the contract. ## Core Features & Use Cases - Surface and code map: Entry points, flags, and file:line references for lci search, lci grep, the MCP search tool, and POST /search, down to the trigram bloom, postings index, and scoring functions. - Invariants and traps: Documents certified-absence narrowing, regex literal-seed rules, the 0-based byte column contract, and MCP result caps so changes do not reintroduce silent-zero bugs. - Honest product comparison: Benchmarks and claims (sub-millisecond search, 80% context reduction) checked against ripgrep, Zoekt, Sourcegraph, and embedding search, with measured gaps called out. - Use Case: When fixing a bug where lci grep -E refuses a pure-meta regex, use this Skill to find the seed-extraction logic in src/cli/grep_filters.cpp, the pinning tests, and the probe commands to reproduce it. ## Quick Start Use the lci-search skill to locate the code and tests behind lci search ranking and compare it against ripgrep.