Ailang Tools
Install ailang-tools when you develop AILANG or its Go runtime in Claude Code and want LSP-backed diagnostics, navigation, and symbols inside the editor agent loop.
Overview
ailang-tools is a plugin marketplace for the Build phase that adds AILANG and gopls language server integrations for Claude Code development.
What is this marketplace?
- Two repo-local plugins: ailang-lsp and ailang-go-lsp
- ailang-lsp runs `ailang lsp --stdio` for .ail files with diagnostics, hover, go-to-def, references, and document symbols
- ailang-go-lsp wraps gopls for the AILANG Go implementation with instant diagnostics and navigation
- JSON Schema marketplace manifest for Claude Code plugin discovery
- Requires `ailang` and `gopls` binaries on PATH respectively
- Marketplace contains 2 plugins: ailang-lsp and ailang-go-lsp
- ailang-lsp uses `ailang lsp --stdio`; ailang-go-lsp requires gopls on PATH
Community signal: 31 GitHub stars.
What problem does it solve?
Building AILANG in an agent-first editor without LSP support means slow manual compile checks and weak navigation across .ail and Go implementation files.
Who is it for?
Solo developers working in the sunholo-data AILANG repo or forks who already use Claude Code as their primary coding surface.
Skip if: Teams not using AILANG or Go gopls, or builders seeking deployment, SEO, or non-editor automation plugins.
What do I get? / Deliverables
After adding the marketplace you get stdio LSP plugins that surface diagnostics, types, definitions, and symbols while the agent edits AILANG projects.
- Two installed LSP plugins from the ailang-tools marketplace
- Save-time diagnostics and navigation for .ail and Go files in Claude Code
- Schema-valid marketplace entry for repo-local plugin distribution
Plugins in this marketplace
2 plugins — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Language server plugins land in Build because they improve how you write and refactor the product codebase during implementation, not at launch or ops monitoring. Integrations subphase fits because both plugins bridge Claude Code to external LSP binaries—gopls and ailang lsp—on the developer PATH.
How it compares
LSP integration marketplace for a specific language stack, not a general AI agent methodology bundle.
Common Questions / FAQ
Who is Ailang Tools for?
It is for AILANG contributors and experimenters who want Claude Code to behave like an LSP-aware IDE for .ail sources and the Go-based runtime.
When should I use Ailang Tools?
Use it during active Build work on AILANG grammar, tooling, or Go backend code whenever you need live diagnostics and symbol navigation in the agent session.
How do I add Ailang Tools to my agent?
Clone or open the AILANG repo, register the Ailang Tools marketplace manifest, install ailang-lsp and ailang-go-lsp, and ensure `ailang` and `gopls` are on your PATH.