wado / wado-from-idl
AGENTS.md120 starsChanged 14 days agoMITView on GitHub
Generates Wado binding modules from IDL files: the stdlib from WIT, and package-web from WebIDL. - wasi:* — the WASI P3 bindings in wado-compiler/lib/wasi/, generated from wasmtime's WIT. Regenerate with mise run update-stdlib-wasi; it requires the vendor/wasmtime submodule. - core:kiln, core:eval, core:coverage, core:fuel and core:process — the submodules under wado-compiler/lib/core/kiln/, lib/core/eval/, lib/core/coverage/, lib/core/fuel/ and lib/core/process/. Regenerate with mise run update-stdlib-core-wit. The facades lib/core/kiln.wado, lib/core/eval.wado, lib/core/fuel.wado and lib/core/process.wado are hand-written and must be preserved; core:coverage has none, since only core:rt calls…
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-host/AGENTS.mdAGENTS.md
- wado-lsp/AGENTS.mdAGENTS.md
- wado-manifest/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-from-idl
Generates Wado binding modules from IDL files: the stdlib from WIT, and
package-web from WebIDL.
Generated Modules
wasi:*— the WASI P3 bindings inwado-compiler/lib/wasi/, generated from wasmtime's WIT. Regenerate withmise run update-stdlib-wasi; it requires thevendor/wasmtimesubmodule.core:kiln,core:eval,core:coverage,core:fuelandcore:process— the submodules underwado-compiler/lib/core/kiln/,lib/core/eval/,lib/core/coverage/,lib/core/fuel/andlib/core/process/. Regenerate withmise run update-stdlib-core-wit. The facadeslib/core/kiln.wado,lib/core/eval.wado,lib/core/fuel.wadoandlib/core/process.wadoare hand-written and must be preserved;core:coveragehas none, since onlycore:rtcalls it.wado-lang:web—package-web/src/dom.wadoand its browser gluepackage-web/glue/dom.js, generated from the WebIDL snapshotpackage-web/idl/dom.webidl.json. Regenerate withmise run update-package-web;tests/web_dom_is_fresh.rsfails when either is stale. The snapshot is the webidl2 AST of the slicescripts/webidl/snapshot.mjstakes from@webref/idl; widen the slice there and runmise run update-webidl-snapshot. Seedocs/wep-2026-04-01-web.md.
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.

