wado / wado-manifest
AGENTS.md120 starsChanged 14 days agoMITView on GitHub
wado.toml parsing and validation, wado.lock management, and dependency resolution. See README.md for the crate's scope and status, and WEP: Package Manifest for the specification. - This crate must compile for wasm32-unknown-unknown. CI enforces it. - It performs no I/O — no filesystem, no network, no env. Fetching is injected by wado-cli through the DependencyProvider seam; reading the disk belongs to the filesystem CompilerHost (wado_lsp::host::discovery). Keep both boundaries: this crate says where a dependency belongs, never what is there.
In this repository37 other files it gives its agents.
- AGENTS.mdAGENTS.md
- benchmark/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- package-gale/AGENTS.mdAGENTS.md
- package-grog/AGENTS.mdAGENTS.md
- package-jade/AGENTS.mdAGENTS.md
- package-loam/AGENTS.mdAGENTS.md
- package-re/AGENTS.mdAGENTS.md
- package-wadopoet/AGENTS.mdAGENTS.md
- wado-cli/AGENTS.mdAGENTS.md
- wado-compiler/AGENTS.mdAGENTS.md
- wado-from-idl/AGENTS.mdAGENTS.md
- wado-host/AGENTS.mdAGENTS.md
- wado-lsp/AGENTS.mdAGENTS.md
- wado-run-pjrt/AGENTS.mdAGENTS.md
- wado-run-webgpu/AGENTS.mdAGENTS.md
- wado-vscode/AGENTS.mdAGENTS.md
- benchmarkSkill
- ci-timingSkill
- code-review-responseSkill
- coverage-investigationSkill
- crSkill
- debuggerSkill
- distillSkill
- git-upstream-syncSkill
- jcoSkill
- markdownSkill
- on-task-doneSkill
- optimizer-debugSkill
- profiling-wado-compilerSkill
- pull-requestSkill
- rust-renameSkill
- rustSkill
- vendor-submodulesSkill
- wado-cliSkill
- wado-performanceSkill
- wasm-optSkill
The file
Files
wado-manifest
wado.toml parsing and validation, wado.lock management, and dependency
resolution. See README.md for the crate's scope and status, and
WEP: Package Manifest for the
specification.
Rules
- This crate must compile for
wasm32-unknown-unknown. CI enforces it. - It performs no I/O — no filesystem, no network, no env. Fetching is injected
by
wado-clithrough theDependencyProviderseam; reading the disk belongs to the filesystemCompilerHost(wado_lsp::host::discovery). Keep both boundaries: this crate says where a dependency belongs, never what is there.
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
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.

