wado / package-grog
AGENTS.md120 starsChanged 14 days agoMITView on GitHub
Grog is Protocol Buffers for Wado: a Kiln generator that reads a .proto, and the runtime the generated code encodes and decodes through. Development stays inside this directory: - TODO.md — open work. - WEP: Grog — the design and why. - tests/proto/README.md — where the .proto corpus comes from and how it is refreshed. The rules come from the specification, vendor/protobuf-spec: content/programming-guides/encoding.md is the wire format, and content/reference/protobuf/ the grammar. - src/lib.wado — the runtime: encode, decode, merge, and…
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-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
- vendor-submodulesSkill
- wado-cliSkill
- wado-performanceSkill
- wasm-optSkill
The file
Files
Grog Development Guide
Grog is Protocol Buffers for Wado: a Kiln generator that reads a .proto, and
the runtime the generated code encodes and decodes through. Development stays
inside this directory:
TODO.md— open work.- WEP: Grog — the design and why.
tests/proto/README.md— where the.protocorpus comes from and how it is refreshed.
Sources
The rules come from the specification, vendor/protobuf-spec:
content/programming-guides/encoding.md is the wire format, and
content/reference/protobuf/ the grammar.
Layout
src/lib.wado— the runtime:encode,decode,merge, and theMessage,EnumerationandScalartraits the generated code implements.src/parse.wadoreads a.protointosrc/schema.wado's declarations, through the Gale-builtgrammar/Protobuf.g4.src/emit.wadowrites those declarations as Wado;src/generator.wadois the Kiln entry around it.tests/roundtrip/is a consumer package: it imports schemas through Kiln and round-trips them.
Running tests
wado test package-grogThat walks tests/roundtrip/ as well. Loam decodes ONNX through Grog, so a
change to the runtime or to what the generator emits also runs
wado test package-loam/src.
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.

