A practical guide to configuring Claude Code with LSPs, MCPs, and language-specific plugins to enable self-correction in unfamiliar languages. Covers three stacks: Godot/GDScript (using a Godot MCP server and GDScript LSP), Elixir (elixir-ls plus Phoenix-specific skills plugins), and Rust (rust-analyzer LSP plus rust-skills). The core idea is building a 'harness' — a feedback loop that lets Claude detect and fix its own errors, similar to how TypeScript's compiler already does this automatically. Also covers using Chrome DevTools MCP for frontend feedback and Claude Code's auto mode to reduce manual approval friction once a solid harness is in place.
Table of contents
The easy case: TypeScriptFeedback loops, or: what a "harness" actually isWhat an LSP is, and how to give Claude oneThree stacks, same patternThe browser counts tooAuto mode: now you can actually walk awayConclusionReferencesSort: