AmadoMuerte
AmadoMuerte'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 @AmadoMuerte 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 Waxlight-launcher corpus
AmadoMuerte/Waxlight-launcher: Waxlight Launcher is a modern, lightweight and cross-platform launcher for Vintage Story
- Look up how Waxlight-launcher implements vintage-story, vintage-story-mod, vintagestory, with answers cited to file and line.
- Reuse a worked example: the commit “place card actions over cover artwork” (6 files · TypeScript).
- Answer from Waxlight-launcher's real TypeScript source instead of memory (API design and specification).
- Where does Waxlight-launcher handle “place card actions over cover artwork”?
- How does Waxlight-launcher implement vintage-story?
- What does frontend do in Waxlight-launcher?
Search the GitHub repository AmadoMuerte/Waxlight-launcher with XERJ (https://hub.xerj.org/corpus/amadomuerte--waxlight-launcher). 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/AmadoMuerte/Waxlight-launcher Waxlight-launcher && git -C Waxlight-launcher checkout fc2c2d9fd560100f75db4fd386ca87348f2dbb25 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./Waxlight-launcher --url http://127.0.0.1:9200 --prefix waxlight-launcher --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: GPL-3.0. Read it for the approach only, do not copy code.
corpus amadomuerte--waxlight-launcher · API design and specification
Related corpora: spectral, graphql-composite-schemas-spec, connect-protocol, github-api-description
Search an OpenAPI spec from an agent · Case study: reference coding for agents
Selected work
AmadoMuerte/Waxlight-launcher
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/AmadoMuerte)
Included with the author's permission (email, 2026-10-22), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.