Developer tools for the LID (Linked-Intent Development) methodology — keep design intent permanently linked to running code.
LID answers one recurring problem: you know what the code does, but you've lost track of why it exists and whether it still does what the design said it should. This tooling enforces the link between requirements, design docs, and code citations — providing two payoffs: navigation (intent walkable through your editor) and attestation (coherence verifiable by grep). Both work in your editor, your CI pipeline, and your AI workflow.
| Tool | What it does |
|---|---|
| VS Code extension | LSP diagnostics, hover, go-to-definition, rename, completion, visual Intent Navigator |
| IntelliJ IDEA plugin | LSP diagnostics, hover, go-to-definition, find references, rename, completion, and visual Intent Navigator for all JetBrains IDEs |
lidc CLI |
lidc check for CI, lidc init to scaffold new projects, lidc status for a quick summary |
lid-mcp MCP server |
13 tools so AI agents can read and write LID projects with full integrity guarantees |
# 1. Install (macOS/Linux via Homebrew)
brew tap EtaCassiopeia/lid && brew install lid-tooling
# 2. Scaffold a new LID project
lidc init
# 3. Run coherence checks (use in CI)
lidc check
# 4. See spec coverage
lidc statusFull documentation: etacassiopeia.github.io/lid-tooling
| Page | Contents |
|---|---|
| Installation | VS Code Marketplace, JetBrains Marketplace, Homebrew, curl, Windows, from source |
| VS Code extension | LSP features, Intent Navigator, commands, settings |
| IntelliJ IDEA plugin | LSP features, Intent Navigator, actions, settings, plugin signing |
lidc CLI reference |
Commands, check IDs, exit codes, CI integration |
| MCP server | Configuration, all 13 tools, agent workflow |
| Project layout | Schema v2, index.yaml, spec format, citation format |
| Contributing | Building from source, release pipeline, required secrets |
MIT OR Apache-2.0 — see LICENSE-MIT and LICENSE-APACHE.