agentleFS
wado-langwado-lang/wado/.claude/skills/vendor-submodules/SKILL.md

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.

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
  1. Very specific:

    Keep the stanza on a throwaway branch.

    line 66

≈ “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.

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

What is under vendor/

  • vendor/wasm/ - WebAssembly/spec
  • vendor/wasi/ - WebAssembly/WASI
  • vendor/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
  • vendor/wasmtime/ - a Wasm runtime with WASI P3 support
  • vendor/wasm-tools/ - the Wasm toolchain the Wado compiler builds on
  • vendor/antlr4/ - ANTLR4, the grammar dialect Gale targets. Read package-gale/AGENTS.md first: most of this tree must not be read
  • vendor/wasi-webgpu/ - the wasi:webgpu proposal
  • vendor/protobuf-spec/ - protobuf.dev's source, which is the protobuf spec
    • Wire format: vendor/protobuf-spec/content/programming-guides/encoding.md
    • The .proto grammar, 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
  • vendor/protobuf/ - protocolbuffers/protobuf, for the .proto files the spec does not carry: src/google/protobuf/descriptor.proto, the well-known types, and the unittest*.proto / test_messages_*.proto Grog parses as a corpus
  • vendor/ecma262/ - tc39/ecma262, the ECMAScript specification, which Re's pattern syntax follows
    • Patterns: vendor/ecma262/spec.html, chapter RegExp (Regular Expression) Objects
    • The properties \p{…} takes: vendor/ecma262/table-*-unicode-properties*.html
  • vendor/test262/ - tc39/test262, ECMAScript's conformance tests. Re's corpus is test/built-ins/RegExp/ and test/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 $ref reaches under remotes/

git submodule update --init --recommend-shallow fetches them.

Syncing

mise run sync-vendor

vendor/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 of StoreOpaque::current_thread so the fast path inlines. Removes ~1 point of CPU; throughput flat.
  • trace_fiber_roots.patch — tracks fiber-owning reps instead of scanning the whole component ResourceTable per GC. Not measurable.

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.