How to write code when your compiler speaks English.
- LID is the language.
- Claude is the compiler.
- Code is the output.
Modern coding agents rarely write bugs. What they write are intent gaps — places where the agent assumed one meaning and you held another. LID closes those gaps by giving your agent a dialect of English it can compile faithfully: specs are source, code is compiled output, and every intent change cascades downstream. A minimum system. Not a factory.
-
/plugin marketplace add jszmajda/lidRegister the marketplace in Claude Code.
-
/plugin install linked-intent-dev@jszmajda-lidInstall the core workflow plugin.
-
/linked-intent-dev:lid-setupBootstrap your project — adds a docs/ tree and LID directives to CLAUDE.md.
See the cascade.
The most persuasive thing about LID isn't the prose — it's watching intent propagate. Describe a change in English. The agent updates the LLD, cascades through the specs, regenerates the tests, and rewrites the code. Two minutes, one real project.
Which path is yours?
Four starting points, depending on where you're coming from. Each one has a short orientation on the Start page.
Evaluating
Decide if LID solves a problem you have. Skim, browse an example, read on.
Orient 02 / PathStarting new
Greenfield project. Install, describe what you want, let the skill walk you through it.
Begin 03 / PathExisting codebase
Brownfield. Map the code first, then layer LID's discipline on top of what exists.
Map 04 / PathScoped to a subsystem
Solo trying LID on one slice of a larger non-LID project. Scoped mode is made for this.
Scope