vendor-submodules
Skill120 starsChanged 16 days agoMITView on GitHub
Locate and sync the reference specs and runtimes vendored under vendor/ — the Wasm, WASI P3, and Component Model specs, and the wasm-tools and wasmtime sources. Use whenever an answer should come from one of those sources rather than memory, and whenever vendor/ is missing or stale.
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-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
- wado-cliSkill
- wado-performanceSkill
- wasm-optSkill
The file
We split this skill 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
- Very specific: line 66
Keep the stanza on a throwaway branch.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill 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.
Files
What is under vendor/
vendor/wasm/- WebAssembly/specvendor/wasi/- WebAssembly/WASIvendor/component-model/- WebAssembly/component-model (CM spec)- Canonical built-ins:
vendor/component-model/design/mvp/CanonicalABI.md - Concurrency (async, streams, futures):
vendor/component-model/design/mvp/Concurrency.md - Explainer:
vendor/component-model/design/mvp/Explainer.md
- Canonical built-ins:
vendor/wasmtime/- a Wasm runtime with WASI P3 supportvendor/wasm-tools/- the Wasm toolchain the Wado compiler builds onvendor/antlr4/- ANTLR4, the grammar dialect Gale targets. Readpackage-gale/AGENTS.mdfirst: most of this tree must not be readvendor/wasi-webgpu/- thewasi:webgpuproposalvendor/protobuf-spec/- protobuf.dev's source, which is the protobuf spec- Wire format:
vendor/protobuf-spec/content/programming-guides/encoding.md - The
.protogrammar, one file per syntax and edition:vendor/protobuf-spec/content/reference/protobuf/{proto2,proto3,edition-2023,edition-2024}-spec.md - Edition features:
vendor/protobuf-spec/content/editions/features.md
- Wire format:
vendor/protobuf/- protocolbuffers/protobuf, for the.protofiles the spec does not carry:src/google/protobuf/descriptor.proto, the well-known types, and theunittest*.proto/test_messages_*.protoGrog parses as a corpusvendor/ecma262/- tc39/ecma262, the ECMAScript specification, which Re's pattern syntax follows- Patterns:
vendor/ecma262/spec.html, chapterRegExp (Regular Expression) Objects - The properties
\p{…}takes:vendor/ecma262/table-*-unicode-properties*.html
- Patterns:
vendor/test262/- tc39/test262, ECMAScript's conformance tests. Re's corpus istest/built-ins/RegExp/andtest/language/literals/regexp/vendor/JSON-Schema-Test-Suite/- json-schema-org's conformance tests, which Jade's validator answers to:tests/draft2020-12/, with the schemas a remote$refreaches underremotes/
git submodule update --init --recommend-shallow fetches them.
Syncing
mise run sync-vendorvendor/wasmtime goes to the exact version in Cargo.lock, which WASI P3
compatibility requires. The other submodules go to their remote HEAD.
Building against a patched wasmtime
To test a change to wasmtime itself, edit vendor/wasmtime in place and add to
the workspace Cargo.toml:
[patch.crates-io]
wasmtime = { path = "vendor/wasmtime/crates/wasmtime" }
wasmtime-wasi = { path = "vendor/wasmtime/crates/wasi" }
wasmtime-wasi-http = { path = "vendor/wasmtime/crates/wasi-http" }
wasmtime-wasi-tls = { path = "vendor/wasmtime/crates/wasi-tls" }Those four names redirect 31 crates. The cranelift-*, pulley-*,
wasmtime-internal-* and wiggle* crates follow through the dependency graph.
sync-vendor already holds the submodule at the Cargo.lock version, so the
sources match what the workspace expects and nothing needs porting.
Keep the stanza on a throwaway branch. CI checks out without submodules
(submodules: false, also actions/checkout's default), so on main every job
dies while parsing the manifest. Landing it means turning submodule checkout on
across every workflow.
reference/ holds patches written this way, each with its measurement:
current_thread_split.patch— splits the cold deferred-frame replay out ofStoreOpaque::current_threadso the fast path inlines. Removes ~1 point of CPU; throughput flat.trace_fiber_roots.patch— tracks fiber-owning reps instead of scanning the whole componentResourceTableper GC. Not measurable.
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.

