AztecProtocolAztecProtocol/aztec-packages/avm-transpiler/CLAUDE.md

aztec-packages / avm-transpiler

CLAUDE.md458 starsChanged 2 months agoApache-2.0View on GitHub

Do not override the toolchain (cargo +nightly, rustup override); rust-toolchain.toml pins it and CI will reject anything else. Outputs are consumed by barretenberg/cpp/ (via the avm_transpiler.h header) and yarn-project/ (via the built static library). After non-trivial changes, rebuild both or cross-component breakage will surface only in unrelated CI steps:

We split this CLAUDE.md 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:
Do not override the toolchain (cargo +nightly, rustup override).
line 11

≈ “Common” is an estimate: at least 1 in 5 of the 25,680 CLAUDE.md 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

CLAUDE.md

avm-transpiler

Build

./bootstrap.sh            # full build
./bootstrap.sh build_native
./bootstrap.sh build_cross <target>   # e.g. arm64-linux, amd64-macos

Do not override the toolchain (cargo +nightly, rustup override); rust-toolchain.toml pins it and CI will reject anything else.

Downstream rebuilds

Outputs are consumed by barretenberg/cpp/ (via the avm_transpiler.h header) and yarn-project/ (via the built static library). After non-trivial changes, rebuild both or cross-component breakage will surface only in unrelated CI steps:

(cd ../barretenberg/cpp && cmake --preset default && cd build && ninja)
(cd ../yarn-project && yarn build)

Download now (ZIP)

In this repository22 other files it gives its agents.
- barretenberg/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- docs/llms.txtllms.txt
- acir-formal-proofsSkill
- adding-benchmarksSkill
- bench-regressionSkill
- capture-app-flowSkill
- chonk-inputsSkill
- ci-logsSkill
- create-issueSkill
- cycleSkill
- fixSkill
- genesis-constantsSkill
- merge-train-infraSkill
- merge-trainsSkill
- noir-sync-updateSkill
- prep-cycleSkill
- release-docsSkill
- release-network-docsSkill
- update-doc-referencesSkill
- updating-changelogSkill

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.

Check your setup, free