Avetis
Avetis'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.
Totals across every corpus @azakhary 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 nixie-fx corpus
azakhary/nixie-fx: Open-source particle and VFX runtimes for PixiJS and Three.js
- Look up how nixie-fx implements particles, pixijs, threejs, with answers cited to file and line.
- Reuse a worked example: the commit “Add opt-in ordered batching for Three unlit VFX surfaces” (23 files · TypeScript, JavaScript).
- Answer from nixie-fx's real TypeScript source instead of memory (API design and specification).
- Where does nixie-fx handle “Add opt-in ordered batching for Three unlit VFX surfaces”?
- How does nixie-fx implement particles?
- What does src/runtime do in nixie-fx?
Search the GitHub repository azakhary/nixie-fx with XERJ (https://hub.xerj.org/corpus/azakhary--nixie-fx). 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/azakhary/nixie-fx nixie-fx && git -C nixie-fx checkout 72515e86d9c4b1f24a22c8deb4e9dbf3dfa61e9b 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./nixie-fx --url http://127.0.0.1:9200 --prefix nixie-fx --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: MIT. Keep the copyright notice and credit the authors.
corpus azakhary--nixie-fx · API design and specification
Related corpora: in-solidarity-bot, atoma-run--atoma, j03rul4nd/ifc-viewer-online, io-gui/io
Search an OpenAPI spec from an agent · Case study: reference coding for agents
Selected work
azakhary/nixie-fx
The corpus is the whole repository at the pinned commit, not only the files of the selected commit.
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.
Sign in with GitHub or Hugging Face to see more: every selected commit in full (commit date, every folder, licence review state, pin) and the pack builds of each corpus.
[](https://hub.xerj.org/contributors/azakhary)
Included with the author's permission (email, 2026-10-21), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.