lci-feature-map

Routes lci code-lookup and product-comparison questions to the matching feature-area skill.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/standardbeagle/lci-cpp --skill lci-feature-map-standardbeagle
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lci-feature-map
Source: https://github.com/standardbeagle/lci-cpp/tree/main/.agents/skills/lci-feature-map
Command: npx skills add https://github.com/standardbeagle/lci-cpp --skill lci-feature-map-standardbeagle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working in the lci (Lightning Code Index) C++ codebase, it is hard to know which of the many feature-area skills covers a given question about search, symbol navigation, indexing, the MCP server, or configuration. This Skill acts as a router that maps surfaces and questions to the correct lci-* area skill. ## Core Features & Use Cases - Surface-based routing: A table maps CLI verbs, MCP tools, HTTP routes, and subsystems (trigram index, call graph, tree-sitter parsing, git analysis) to one of 13 feature-area skills. - Question-based routing: Directs "where is X implemented" and "how does lci compare to product Z" questions to the right area skill's code map, probe recipes, and product-comparison sections. - Feature set overview: Summarizes lci's surfaces, index architecture, 13 supported languages, analysis capabilities, and operations model on one screen. - Use Case: You ask "where does lci handle MCP tool registration?" and the router points you to the lci-mcp-server skill, which carries the code map and traps for that area. ## Quick Start Ask which lci feature-area skill covers a question about lci search, symbols, indexing, MCP, or config, then follow the routed skill.

Frequently Asked Questions about lci-feature-map

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find where an lci feature is implemented?▼

Use the routing table to pick the feature-area skill matching the surface you are looking at, such as lci-search for trigram search or lci-mcp-server for tool registration. Each area skill carries a code map, probe recipes, and tests that pin the feature.

Which skill covers lci MCP tools and JSON-RPC?▼

The lci-mcp-server skill covers lci mcp, JSON-RPC framing, tool registration and schemas, validation, error conventions, and the info, index_stats, and debug_info tools. The router's surface table maps these directly to that skill.

How does lci compare to ripgrep, ctags, or Sourcegraph?▼

Each feature-area skill contains a product-comparison section for its area, covering ripgrep, ctags, LSP, Sourcegraph, Zoekt, Cursor, Aider, Serena, SonarQube, and CodeScene. For measurement procedure, the router points to lci-benchmarks-evaluation.

What languages and surfaces does lci support?▼

lci supports 13 languages via vendored tree-sitter grammars, with cross-file import resolution for a subset. Surfaces include a CLI with verbs like search, grep, def, refs, and git-analyze, an HTTP API over a Unix socket with 20 routes, and an MCP server over stdio with 15 registered tools.

When should I fall back to grep instead of lci?▼

The navigation rule says to use the built lci binary for search, def, refs, tree, and symbols before grep. Fall back to Grep only where lci lacks the capability, and record the gap in the test-iteration-discipline rules file.