Kai Aldag

Corpus Hub contributor since 2026-10-20

Kai Aldag's work was selected for the XERJ Corpus Hub, the open reference memory AI coding agents search before they write code. When an agent meets the same problem, it gets this implementation back as a worked example, with the author and the repository attached.

1corpus

1selected commit

12files

807lines

★ 3GitHub stars on repo

Totals across every corpus @KaiCode2 appears in; a commit selected for two corpora counts once. Files and lines count the selected commits; each corpus indexes the whole repository at its pinned commit.

What an agent can do with the evm-amm-state corpus

KaiCode2/evm-amm-state: KaiCode2/evm-amm-state (Rust)

Reuse a worked example: the commit “Narrow Slipstream NFT traffic without dropping staking evidence” (12 files · Rust).
Answer from evm-amm-state's real Rust source instead of memory (API design and specification).

Example questions

Where does evm-amm-state handle “Narrow Slipstream NFT traffic without dropping staking evidence”?
What does src/adapters do in evm-amm-state?

Paste it into your AI agent. It clones the repo at the pinned commit and indexes it on your machine.

Search the GitHub repository KaiCode2/evm-amm-state with XERJ (https://hub.xerj.org/corpus/kaicode2--evm-amm-state).
Run these in a shell, in order, and check each result before the next:
1. xerj --help  (success: it prints usage). If xerj is missing: curl -fsSL https://xerj.org/get | sh
2. git clone https://github.com/KaiCode2/evm-amm-state evm-amm-state && git -C evm-amm-state checkout 6e307145b4a8b70ca3cff4b5d001ed5b028f037c
3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data
4. xerj autoindex ./evm-amm-state --url http://127.0.0.1:9200 --prefix evm-amm-state --progress plain
5. xerj autoindex map --url http://127.0.0.1:9200
Then answer my question from the indexed files and cite the ax_path of every hit. Query syntax: https://xerj.org/llms.txt
Licence: Apache-2.0. Keep the copyright notice and credit the authors.

corpus kaicode2--evm-amm-state · API design and specification
Related corpora: connect-protocol, openapi-moonwalk, rust-api-guidelines, digitalocean-openapi
Search an OpenAPI spec from an agent · Case study: reference coding for agents

Selected work

GitHub ★ 3

KaiCode2/evm-amm-state

6e307145b4 Narrow Slipstream NFT traffic without dropping staking evidence

selected commit: 12 files · 807 lines · Rust · src/adapters, tests

The corpus is the whole repository at the pinned commit, not only the files of the selected commit.

selected · in licence reviewcorpus kaicode2--evm-amm-stateAPIApache-2.0 agreed 2026-10-20

Not installable yet: this corpus is not in the hub registry until its licence review passes, so xerj corpus add and xerj ask cannot fetch it. It becomes installable when this card says live in the hub.

[![XERJ Corpus Hub contributor](https://hub.xerj.org/contributors/KaiCode2/badge.svg)](https://hub.xerj.org/contributors/KaiCode2)

Included with the author's permission (email, 2026-10-20), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.