agentleFS
wado-langwado-lang/wado/wado-lsp/AGENTS.md

wado / wado-lsp

AGENTS.md120 starsChanged 14 days agoMITView on GitHub

The language service engine and the stdio LSP server. Scope and build targets are in WEP: LSP Architecture; how each part works is in its module doc. Open work is in TODO.md, and the LSP specification at <https://microsoft.github.io/language-server-protocol/specifications/lsp/3.18/specification/>. - The crate compiles for wasm32-unknown-unknown (CI-enforced), so the browser playground runs it without a WASI host. Runtime I/O is the host's: wado-cli on the desktop, an in-memory host in the browser. - Every AST walk goes through wado_compiler::ast::AstVisitor and its walk_*…

The file

We split this AGENTS.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every AST walk goes through wado_compiler::ast::AstVisitor and its walk_* functions.

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

wado-lsp

The language service engine and the stdio LSP server. Scope and build targets are in WEP: LSP Architecture; how each part works is in its module doc. Open work is in TODO.md, and the LSP specification at https://microsoft.github.io/language-server-protocol/specifications/lsp/3.18/specification/.

Rules

  • The crate compiles for wasm32-unknown-unknown (CI-enforced), so the browser playground runs it without a WASI host. Runtime I/O is the host's: wado-cli on the desktop, an in-memory host in the browser.
  • Every AST walk goes through wado_compiler::ast::AstVisitor and its walk_* functions. A hand-written traversal silently skips whatever a later AST node adds.
  • A query degrades to no answer on a partial Semantics, never fails: the frontend always produces one, and batch compilation alone checks Semantics::is_complete().
  • A CompilerHost wrapper delegates every capability. A trait default in its place drops the wrapped host's dependency index (DiagnosticCollector).
  • A file: URI is percent-decoded on the way in (Uri::to_filename) and re-encoded on the way out (location::filename_to_uri). Clients key documents by URI string, so a path that skips either names a different document.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.