Carlos Rodriguez
Carlos Rodriguez'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 @eduardocque 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 plitzi-workspace corpus
Plitzi/plitzi-workspace: Plitzi/plitzi-workspace (TypeScript)
- Reuse a worked example: the commit “some changes in authoring, builder, and related to the docs” (32 files · TypeScript).
- Answer from plitzi-workspace's real TypeScript source instead of memory (API design and specification).
- Where does plitzi-workspace handle “some changes in authoring, builder, and related to the docs”?
- What does apps/builder do in plitzi-workspace?
Search the GitHub repository Plitzi/plitzi-workspace with XERJ (https://hub.xerj.org/corpus/plitzi--plitzi-workspace). 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/Plitzi/plitzi-workspace plitzi-workspace && git -C plitzi-workspace checkout 61271756640f21a27b739823f0af5e7c60b3ccd2 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./plitzi-workspace --url http://127.0.0.1:9200 --prefix plitzi-workspace --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: AGPL-3.0. Read it for the approach only, do not copy code.
corpus plitzi--plitzi-workspace · API design and specification
Related corpora: redoc, openapi-moonwalk, arazzo-spec, openapi-spec
Search an OpenAPI spec from an agent · Case study: reference coding for agents
Selected work
Plitzi/plitzi-workspace
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/eduardocque)
Included with the author's permission (email, 2026-10-19), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.