lsp-architecture

Topics in the source

• lsp-architecture
• Depth Controls (hard limits)
• Step 0 — Initialize
• Step 1 — Language Detection
• Step 2 — Package Structure
• Step 3 — Entry Points
• Step 4 — Hotspot Analysis
• 4a — Find candidate files

Requires the agent-lsp MCP server. Generate a structural architecture overview of any codebase: language distribution, package hierarchy, entry points, dependency flow, and hotspot files. One invocation for the big picture. Read-only; does not modify any files. Invocation: User provides the workspace root path (e.g. "/home/user/myproject"). If omitted, use the current working directory. -- These limits are strict constraints. Never exceed them: Package enumeration: cap at 30 packages Hotspot analysis: cap at 10 files Workspace symbol queries: cap at 5 queries Do NOT recurse into vendor/, nodemodules/, .git/, or other dependency directories -- If LSP is not yet running, start it with the workspace root: Then detect which language servers are available: Record the available languages and their file globs. This determines which queries to run in later steps. -- Scan the workspace to determine language distribution. Use file extension counts from the detected servers and supplement with a filesystem scan (via Glob tool) to count files per language. For each detected language, report: Language name File count Estimated lines of code (sample 3-5 representative files and extrapolate) Skip

This is an excerpt. Refer to the complete source and its current requirements.